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 mapping validation #97

Open
codingjoe opened this issue Sep 19, 2018 · 1 comment
Open

Add mapping validation #97

codingjoe opened this issue Sep 19, 2018 · 1 comment

Comments

@codingjoe
Copy link
Contributor

Hi,

currently when you import a new mapping, there is not way to know if it will actually work or not. The mapping will always be accepted and eventually your connection state will switch to error.

That behavior makes deployments ever so more risky. Therefore I would suggest to add a new command, something like connect:validate FILE to send a file via API and wait for a response if the mapping could be successfully applied based on the connected Salesforce instance.

I am aware that there are certain limitations that can not easily be overcome, due to the Salesforce API.
But the Heroku Connect interface has a fairly good understanding of the Object and fields structure of the salesforce instance. It is also aware of certain constrains and even displays warnings.

I would assume that this information could be made accessible via the API. But I would suggest to keep it simple. Any kind of validation is better then none. This would be our priority list:

  1. Objects and Fields exist
  2. Required fields are in the mapping
  3. Required indexes are added
  4. Polling is not available

I hope that helps a bit, we would certainly appreciate such a feature. We could build the plugin part, but you guys need to provide the API.

Best
-Joe

@codingjoe codingjoe changed the title Add mapping validation (prior to import) Add mapping validation Sep 19, 2018
@sigmavirus24
Copy link
Contributor

Thanks for this @codingjoe. I'm going to pass this along to the appropriate folks to be considered. 🎉

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

No branches or pull requests

2 participants