Brian Freytag
10/31/2019, 1:17 PMjobJoin
requires a JobSearchBasic
and the entityId
field only accepts a SearchStringField
. It seems like the only "identifiers" that allow multi select are internalId
and `externalId`; However, we can't reliably use those values due to internal usage of the systems and IDs getting mismatched.
We have a homespun ERP that pushes Project, Customer, and Sales Order data into Netsuite after it is awarded on our end. We send the externalId
and then we store the Netsuite internalId
in our database. The entityId
we send is identical to the externalId
. However, we have customers who have subsidiary companies who, after the Project has been awarded, decide that they want to issue the PO from a different subsidiary. Due to a limitation in Netsuite, you can't change a Customer of a Project after a certain point (which we cross when we put the data in Netsuite from our system). So the sales team will create a new Project in Netsuite, transfer the costs, archive the old Project, and then just go into our ERP and change the company and contacts and move on. As you can suspect, this doesn't create the externalId in the new Netsuite Project, nor does it update the Netsuite Project's internalId in our System.
When the projects are archived, they change the entityId
of the old one and use the same one on the new Project, so that is really the only field that we can trust at this point.