If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
Information Needed
To help us with upgrading your instance please make sure to:
Made some new test, same problems. Look at this order number instead: 1604271722546553744
SF org ID: 00D6100000084Y8
Updated: I have discovered the problem; although all the data from the custom question is coming through, only the *last option checked* is being picked up by the custom mapping.
ex: If someone puts checks next to options 1-3 on the donation form, only option 3 is successfully mapped, even though all the options have mapping attached to them.
Does this mean that single word answers should be fine? My experience was that double words did work, but that the bug was for the final check marks on the form. Ex order number: 1604271919116529962
On further investigation, I've found that your answer is not correct and my suspicion is...the issue is not two word answers, but something to do with "exit after last match." Only the final matching item in the custom question is being mapped, regardless of how many words it is.
Is there any work around you can imagine for this issue? I am on a May 1st deadline for this functionality working.
We have identified an issue with 2 words and have shown that to be true in our testing which has been resolved in the update. You may be experiencing a related issue or different but we are sure of a bug in here.
As for exit after last match-- yes the system will update the fields and the same field may be updated multiple times but the last one will naturally prevail.
If you wish to elaborate on what you see we will gladly review it.
The next update is due out on May 15 as testing is in progress so it won't be able to be released earlier.
The beta releases are available for testing and are in the Salesforce beta section of the forum.
Salesforce will finish deployment of Summer '16 release by June 11 and as such we were unable to release in May. We have to wait for all instances to be updated to Summer '16 before releasing it since those instances not yet on Summer '16 will not be able to install the apps.
Currently the release date is June 15, after Salesforce's completion of all updates. Please see the release notes in the Beta channel.
Let us know if we can be of any further assistance.
I don't see the fix to this issue listed in the Beta, but maybe I'm just missing it...would you recommend installing the Beta now or waiting until June?
We do NOT recommend installing the beta in any production instance. Our dev instances are now on Summer '16 release of Salesforce and all pages are being converted to the latest API version of Salesforce. The testing team is testing each page for compatibility and backward issues, if any. We do not recommend updating the latest beta, and if your instance has not yet been updated to Summer '16 you will get an error when trying to upgrade as the instance & version are not compatible until your instance is at Summer '16 release.
Comment