i have a custom transaction that works on all subsidiaries except a newly one created how can i fix this?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** If your custom transaction is not working for a newly created subsidiary, it could be due to the subsidiary settings in your custom transaction. The subsidiary field in a transaction determines what items, accounts, etc., can be accessed on that transaction. If the subsidiary is not set correctly, it may not show the correct accounts or items. Here are a few steps you can take to troubleshoot this issue: 1. Check the subsidiary settings in your custom transaction. Make sure that the new subsidiary is included in the list of subsidiaries that can use this transaction. 2. Check the accounts and items associated with the new subsidiary. Make sure they are set up correctly and are accessible for the custom transaction. 3. If the new subsidiary is a child of another subsidiary, you might need to adjust the subsidiary hierarchy. You can do this by enabling subsidiary hierarchy modifications and moving the transactions subsidiary down and creating a new parent. 4. If the issue persists, you might need to create a workflow or script to set the subsidiary field value before the record load for all the transactions. Please note that workflows might have issues setting subsidiaries in some transactions, and transactions also source the subsidiary from the Customer. So it might be a consideration to set your customers to that Primary subsidiary. Remember to test any changes in a sandbox environment before applying them to your live environment.