Getting the error message "Invalid location reference key for subsidiary." for a Transfer Order CSV Import. The location the error mentions is active and has inventory for the item to be transferred. The location has the subsidiary selected correctly, as well.

AI generated answer (using internal Slack threads):

Based on the conversations, the error message "Invalid location reference key for subsidiary." during a Transfer Order CSV Import could be due to a few reasons: 1. The location field in your CSV might not be correctly formatted. Ensure that the location field does not contain any special characters like colons. If you're using the internal ID for the location, make sure that you're changing the mapping to use the internal ID instead of the name. 2. The error could also be due to a mismatch between the location and the subsidiary. This could happen if an existing workflow or script is setting the location based on outdated business rules. You might need to update these rules to ensure that the correct location is set for each subsidiary. 3. Another possible reason could be that the account associated with the subsidiary in your CSV is not valid. The system might not be able to "see" the subsidiary you're trying to reference, meaning the subsidiary is inactive or the role you're using doesn't have access to it. Or the reference key for the subsidiary does not exist. Make sure that the subsidiary is active and that your role has access to it. 4. Lastly, ensure that the location is on a sublist level for things like this. Remember to double-check your CSV for any errors and try to manually enter a few lines of the transfer order via the UI to see if you can select the location and subsidiary. If you can, then the error is likely due to some issue with your CSV. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******