Betsy Barefoot
06/11/2024, 2:11 PMAn error occurred with resolving custom object references.
Details: The script id '[scriptid=customrecord_che_package.custrecord_package_trx_id]' referenced by the field 'sourcefrom' in subrecord custrecord_che_pkg_purchase_trx (customrecordcustomfield) could not be resolved.
File: ~/Objects/customrecord_che_job_posting.xml
Object: customrecord_che_job_posting.custrecord_che_pkg_purchase_trx (customrecordcustomfield)
I'm not sure how to resolve it. Thoughts? Is it a bad idea to manually create those two fields in production and then continue on with webstorm to create the remaining fields on the objects?
Thanks in advance!Anthony OConnor
06/11/2024, 3:25 PMcustrecord_package_trx_id
field reference another custom record that's part of the deployment?
you might just be able to rearrange the objects in your directories...
create sub directories to control the order they're created, or create a non-deploy directory outside of objects, move the problem record to that folder, then deploy once, then move it back and deploy againAnthony OConnor
06/11/2024, 3:26 PMBetsy Barefoot
06/11/2024, 3:35 PMcustrecord_package_trx_id
- is a list/record field, using Transactions - so not part of the custom record deployment
custrecord_che_pkg_purchase_trx
is also a list/record based on Transactions, but sourced by custrecord-package-trx-id
I didn't realized you could reorder the objects or move them. I will try that. I can see from the current order why this would be an issue.
I did inadvertently deploy multiple times and didn't realize initially that the records had been created before the error.
Thank you!Betsy Barefoot
06/13/2024, 1:18 PM