Error:
Bad request: 400 Bad Request: [{"message":"No such column 'Expiry_Date__c' on sobject of type Account","errorCode":"INVALID_FIELD"}]; Error ID 75c97682-19d5-4575-b237-388522ae94b6
What does this mean?:
This error is coming from the Salesforce API complaining about a column Expiry_Date_c not being there. Column in database terms means a field. Whenever you see a field name ending in _c in Salesforce, it means that it is a custom field.
This means that one of the field that Workato has detected was not found in the recipe's schema. A schema is a structure of fields constructs the object. Think of it as a structure that Workato uses to understand and "talk" to your apps. If Workato's schema and the application's schema is different, that means they are both talking in different "dialects", hence it throws an error because there are a few fields that Workato has never seen before in its schema
Solution: In order to resolve this, you can use what we call Refresh schema. There are two levels of schema refresh. One clicks on the refresh schema and save. This refreshes the whole recipe and keeps it updated. Here's an animation to show how it works.
The second method is will refresh schema at a step level. This will refresh the schema for that specific step. You will have to click on the step, change the application to something else, and change it back to the original again. Do take note that this will wipe out all field mappings that you have on that step.
A side effect of this is that the field mappings that were there get invalidated, you will have to remap these fields. To take care of this problem, I either write down the field names that I mapped, or make an temporary clone where I have the original mappings and refer to it as I create my new mappings. Once I am done creating my recipe, I delete the temporary clone.
Have a question? Join our bi-weekly Expert Hour to get help from our Experts. Alternatively, you can find similar questions in our Q&A (Recipe Errors) Forums or Start a New Topic.