Viewing 15 replies - 31 through 45 (of 74 total)
  • Thread Starter jbuchbinder

    (@jbuchbinder)

    I’m not really sure what you’re asking for.

    HTML forms can only eventually pass key/value pairs of strings, no matter what the control (except for file uploads, but that’s another story entirely). To create a date control, you would have to set up logic regarding:

    1. Figuring out which date to pass. This could theoretically be accomplished by using a date picker widget of some sort.
    2. Configuring the string format which is passed via the form. It has to be reduced down to a string, and certain forms are going to want certain date formats. For example, YYYY-MM-DD vs DD/MM/YYYY.
    3. Validation. It has to deal with whether or not the date is potentially valid, if it is picked from a widget. If it’s a static date, that still has to be programmatically defined somewhere.

    What you’re asking isn’t particularly simple. It’s theoretically possible to add an additional set of configuration variables for a form which specify date format and field name to pass the current date as a hidden form variable — but that’s a pretty specific case.

    I just need to pass the date that you hit submit to a field. I would use a rule from salesforce, but y customer is using the group edition and workflow rules are not included.

    Plugin Author Nick Ciske

    (@nickciske)

    For a web to lead entry, isn’t the create date the same thing as the submission date?

    It is. The problem is that I am need to pass a date based on an agreement to terms in a field labeled “Agreed to Terms”

    Thread Starter jbuchbinder

    (@jbuchbinder)

    I suppose we could add a “current_date” type, which takes as opts an optional format for the number, based on PHP’s date formatting syntax:

    https://www.php.net/manual/en/function.date.php

    That would be a big help. I believe many of the plugin users would use it. As I said before, I an not a coder, is this a time consuming process?

    Thread Starter jbuchbinder

    (@jbuchbinder)

    No. The biggest issue at the moment is the conspicuous lack of documentation available for the plugin. Someone really has to sit down and document how this works.

    I’ll add it as described earlier.

    Thread Starter jbuchbinder

    (@jbuchbinder)

    I would be very willing to help with it. I was a procedures documention manager for Submarine Repairs (US Navy) for quite a while.

    The date is not populating. Is there anything required in the options to make this work?

    Thread Starter jbuchbinder

    (@jbuchbinder)

    If you have a github account, I can give you access to the documentation wiki. You’d need to know how to write in Markdown, but otherwise it’s pretty simple.

    You need to populate opts with a PHP date_format formatted field, like Y-m-d for YYYY-MM-DD format, etc. Otherwise it’s going to pass a null value. View the source of the page and you should see it populating a hidden variable.

    I have the date opts formated as required by salesforce Y-m-d and the data shows correctly in the page source, but does not populate salesforce. Otehrs have posted that it only works as date/time because of the api. I have verified that my field names match.

    So i tried witht the date/time format and that does not pass either.

    Thread Starter jbuchbinder

    (@jbuchbinder)

    Okay, if it’s showing up in the source of the page, but for some reason isn’t “showing up” in salesforce, you’re configuring the name of the variable incorrectly somewhere. The plugin is properly populating the hidden field which is meant to be passed to salesforce, so it would have to be a misconfiguration outside of the scope of the plugin, IMO.

    Do you have a way of testing this to see if the date pushes thru at all?

Viewing 15 replies - 31 through 45 (of 74 total)
  • The topic ‘Github fork with some added features’ is closed to new replies.