Current situation or problem: The GOBI integration currently passes through the subaccount value as a text string, rather than performing a lookup against the GOBI organization record.
As such, the value is not validating against the established subaccounts and displays only in view mode, not in edit mode. The order must be un-opened to update the subaccount if desired. If the order is unopened and edited in any other way, there is the danger of eliminating the subaccount since it's not a part of the dropdown list being sourced from the organization record.
- Place an order with the GOBI API.
- Lookup the POL that is generated.
- Edit the POL
Note it seems that GOBI is entering the account number as a string rather than mapping it to an account on the organization record.
Expected result: the GOBI subaccount is listed in the vendor details on the POL edit form. The field is not editable.
Actual result: the GOBI subaccount comes through as a generic string. If you edit the POL, the subaccount is not visible.