Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add settings for Database options #30

Closed
9 of 11 tasks
acrosman opened this issue Jun 3, 2021 · 1 comment
Closed
9 of 11 tasks

Add settings for Database options #30

acrosman opened this issue Jun 3, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@acrosman
Copy link
Owner

acrosman commented Jun 3, 2021

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.

Additionally:

PRs for any individual piece happily considered. Please do not comment that prs that fix a piece will fix or close this issue.

@acrosman acrosman added the enhancement New feature or request label Jun 3, 2021
This was referenced Jul 13, 2021
@acrosman acrosman linked a pull request Jul 15, 2021 that will close this issue
@acrosman acrosman removed a link to a pull request Jul 15, 2021
@allisonletts
Copy link
Contributor

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.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants