transaction country address form no longer correctly setting using setValue GB, it is defaulting to primary subsidiary's default country

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue of the transaction country address form not correctly setting using setValue to GB and defaulting to the primary subsidiary's default country can be addressed in a couple of ways. 1. Override Checkbox: One of the users suggested clicking the override checkbox. This might allow you to manually set the country to GB. 2. Workflow: Another user suggested using a workflow to set the form field value to the desired country. This could be a viable solution if the issue is occurring across multiple records or users. 3. Setting the Country First: In a conversation about setting a foreign country in the addressbook sublist on a vendor record, a user suggested setting the country first before setting other fields. This might be applicable to your situation as well. 4. Using setValue with Country Codes: It was also suggested to use setValue with the 2-letter ISO 3166 country code. For GB, the code would be 'GB'. Here is a sample code snippet:

javascript
subrecAddress.setValue({
    fieldId: 'country',
    value: 'GB' // 2-letter ISO 3166 country code for GB
});

Please refer to the [Country Codes Used for Initialization Parameters](https://system.netsuite.com/app/help/helpcenter.nl?fid=section_4267255811.html#bridgehead_4447485621) for more information on country codes. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******