I am consulting for a client who is using Epicor 10 on-prem I am pretty new to Epicor so had a quick question. I am synchronizing their epicor system with Salesforce. I am trying to create a customer in Salesforce from Epicor Accounts (can do successfully), and then write back the Salesforce ID to a custom field in Epicor. I run into many different errors on write back like “Must be valid Country”, “Must be valid Group Code”, etc.
Does anyone know the list of required fields necessary for Account Updates or Creation via Epicor API?
Honestly, the requirements change based on the modules installed. For example, CRM users have more fields to fill in. Some Country Specific Functionality (CSF) may also have requirements. Your best bet is to run the Customer maintenance program and see what fields are required for base Epicor. Then add the fields that are required by the business processes for your client. The .Net client uses the same logic as the REST API, so flushing it out first in the main client will be your best bet. Also, you can turn on tracing and see the actual traffic going back and forth. If they are on 10.2.500+ then you can abstract away some of that detail from Sales Force and make it an Epicor Function where you can control the signature of the call.
If you have access to the Data Migration Tool, each “BO” will tell you the required fields.
E10 used to work where an update to a record only required the key fields, and any unsupplied field would just remain unchanged. Some now require the “required” fields as well, even if you’re not changing them.
Hi @ckrusen , I believe I found the required fields now. I now see there is a “duplicate entry” error. So, I’ve gotten closer. Any ideas here? I’m using PATCH method to update the Salesforce ID btw. let me know if you may need any other info to help.
I believe Salesforce is more integrated into E10 than just being extra UD fields in the standard tables. There might need to be different BO calls to update the SF info.
Like other’s have said, try doing an update manually (via the UI) with tracing enabled. Then you can see the BO methods called and what data is passed to them.
Not having SF myself, I can’t test anything. One thing to check is that you can change a customers SF ID in the UI. It might very well not allow changes, as that might break referential integrity.