Troubleshooting SFDC Account Record Creation Error

Alex K. · 2024-09-04 19:37:17.713337+00

Hi team - trying to create new Account records in SFDC. This error doesn't make sense because I have a status default already set for new record creation I've tried adding New / "New" / 'New' directly in the side panel and the only thing that seems to work is to reference a text column with New as a cell Example . Any recommendations here?

Troubleshooting SFDC Account Record Creation Error | Clay

12 comments

· Sorted by Oldest

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bo (.
·
·
Hey Alex, I’ve identified one error in this view, and for the other, I re-ran it. The issue was caused by stale data not computing the correct response. It seems that the issue you’re facing is due to an invalid value for a restricted picklist field in Salesforce. Specifically, the error is with the Category__c field, which expects a valid value from a predefined set of options (picklist). The value provided, Chains/DAOs/Foundations/Protocols, isn’t allowed, resulting in the 400 Bad Request response. Here’s how you can resolve it: 1. Check the Salesforce picklist values for the Category__c field to ensure you know what values are valid. 2. Ensure the value being sent (Chains/DAOs/Foundations/Protocols) is included in that picklist. If it’s not, you can: • Update the Salesforce picklist to include this value, or • Adjust your request to match one of the existing valid options. 3. Update the request and retry. If the field values are dynamic, consider adding validation logic before the API request to ensure only valid picklist options are sent. Let me know if you need any further help! 😊 ⬤
Alex K.
·
·
Yes it works but when I remove that as one of the values to update, I still get the original Status error
Alex K.
·
·
Despite New being a default Status and it existing as a value in SFDC
Alex K.
·
·
Here's a screenshot - the error will occur for every field that doesn't have New in the status column
Loading attachments
Bo (.
·
·
I see that “New” works, but when I tried using a test value, it didn’t work. The value needs to match one of the options inside the Status__c field. Since “New” is one of the valid statuses, what other status are you trying to add?
Alex K.
·
·
In other tables, when I create an Account record, this hasn't been a field I typically fill out
Alex K.
·
·
Usually I run Create a Record, leave this empty, and the new Record will default to New
Bo (.
·
·
No worries at all! Now that all the fields have been filled, I can’t view them anymore. Could you create a new table for me, so I can attempt to replicate the issue? 😊 Or maybe record a loom and then leave the table with some errors still so I can try to debug from the backend
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Alex K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Alex K.!

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bo (.
·
·
Hey Alex, I’ve identified one error in this view, and for the other, I re-ran it. The issue was caused by stale data not computing the correct response. It seems that the issue you’re facing is due to an invalid value for a restricted picklist field in Salesforce. Specifically, the error is with the Category__c field, which expects a valid value from a predefined set of options (picklist). The value provided, Chains/DAOs/Foundations/Protocols, isn’t allowed, resulting in the 400 Bad Request response. Here’s how you can resolve it: 1. Check the Salesforce picklist values for the Category__c field to ensure you know what values are valid. 2. Ensure the value being sent (Chains/DAOs/Foundations/Protocols) is included in that picklist. If it’s not, you can: • Update the Salesforce picklist to include this value, or • Adjust your request to match one of the existing valid options. 3. Update the request and retry. If the field values are dynamic, consider adding validation logic before the API request to ensure only valid picklist options are sent. Let me know if you need any further help! 😊 ⬤
Alex K.
·
·
Yes it works but when I remove that as one of the values to update, I still get the original Status error
Alex K.
·
·
Despite New being a default Status and it existing as a value in SFDC
Alex K.
·
·
Here's a screenshot - the error will occur for every field that doesn't have New in the status column
Loading attachments
Bo (.
·
·
I see that “New” works, but when I tried using a test value, it didn’t work. The value needs to match one of the options inside the Status__c field. Since “New” is one of the valid statuses, what other status are you trying to add?
Alex K.
·
·
In other tables, when I create an Account record, this hasn't been a field I typically fill out
Alex K.
·
·
Usually I run Create a Record, leave this empty, and the new Record will default to New
Bo (.
·
·
No worries at all! Now that all the fields have been filled, I can’t view them anymore. Could you create a new table for me, so I can attempt to replicate the issue? 😊 Or maybe record a loom and then leave the table with some errors still so I can try to debug from the backend
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Alex K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Alex K.!