altname standard field not accessible in custom record via workflow

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. ****** Based on the conversations, it seems that you are trying to access a custom record field via a workflow. Here are some points to consider: 1. Ensure that your workflow is set up to run on the custom record you want to manipulate. This should be configured in the overall workflow configuration. Once this is done, the fields for that custom record should be available to manipulate. 2. If the field you are trying to access has a sourcing relationship, it might not be available for mass updates or inline editing. This is because the field is pulling data from a related record, and you cannot just change the value stored. 3. If you are trying to set a List/Record field via a workflow using a text value from another field, you might encounter an error because the system might be expecting the internal id of the transaction, not just the sales order number. One possible solution to this is to use a Dynamic Lookup action, which can automatically populate the list/record before submit based on the value entered in a text field. This can be done without scripting. Remember to check the permissions on the field and the custom record to ensure they are not locked down, which could prevent you from accessing them.