You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
Adding settings to change some behaviors and assumptions about how to translate Salesforce fields.
Please describe the problem you are trying to solve.
Depending on the use case some standard SF fields might be useful in a couple different forms. Having settings to controls those could be helpful. For example, the main record ID field might be more useful in some settings as an auto number, or plain integer than as an SFID. Another example would be RecordTypeIDs being set as the record type name on the assumption it would be translated during later processing.
Proposed Solution
Add the following settings to the preferences:
Allow Picklists to be Varchar(255) instead of Enums.
Make Picklist to string when the Salesforce value is unrestricted.
Include a blank option in all Enums (instead of just null).
Default lookups fields to indexed.
Default to make picklists indexed.
Allow lookups to default to: char(18), varchar(255) (or text when varchars are too numerous).
Allow setting of default value to field default.
Default all text values to empty string instead of null.
My default values aren't being set properly. Defaults for Varchar(255)s are set without being enclosed in single quotes, so they aren't quite working in practice.
Summary
Adding settings to change some behaviors and assumptions about how to translate Salesforce fields.
Please describe the problem you are trying to solve.
Depending on the use case some standard SF fields might be useful in a couple different forms. Having settings to controls those could be helpful. For example, the main record ID field might be more useful in some settings as an auto number, or plain integer than as an SFID. Another example would be RecordTypeIDs being set as the record type name on the assumption it would be translated during later processing.
Proposed Solution
Add the following settings to the preferences:
Additionally:
PRs for any individual piece happily considered. Please do not comment that prs that fix a piece will fix or close this issue.
The text was updated successfully, but these errors were encountered: