Good morning, I am experiencing an issue using the PHP Toolkit (NetSuiteService.php) when creating a Credit Memo with a custom shipping address field.
The Problem:
When we add a Credit Memo via the SOAP API, all standard and custom fields are sent. The record is successfully created. However, the State and Zip fields within our custom shipping address area appear completely empty in the NetSuite User Interface (UI).
The Contradiction:
- API Read vs. UI: If we immediately perform a get or search query for that exact Credit Memo via the API, the response returns the custom State and Zip fields populated with the correct values. The data exists in the API layer but is invisible in the UI.
- Manual Update Behavior: If we manually open the record in the NetSuite UI, type the missing State and Zip into the fields, and click Save, the data stays and is now visible in the UI.
- Post-Manual API Comparison: If we query the record via the API after saving it in the UI, the returned XML payload for those custom address fields is identical to the payload we received before the manual fix. The API sees no difference, but the UI does.
Steps to Reproduce:
- Push a Credit Memo via PHP Toolkit containing custom address fields (including custom State and Zip).
- Open the newly created Credit Memo in the NetSuite browser UI. Observe that State and Zip are blank.
- Fetch the same record via API get. Observe that State and Zip contain the data sent in step 1.
- Manually enter the State and Zip in the UI and save.
- Fetch the record via API get again. Observe the data payload matches the payload from step 3 exactly.
Questions:
- Why is the NetSuite UI failing to render these custom address fields upon API creation, even though the database clearly stores and returns them via SuiteTalk?
- Is there a specific address source, sourcing flag, or subrecord schema behavior we need to trigger in our PHP array to force the UI to recognize and display these values upon insertion?