Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
The customer is experiencing errors in Finance and Operations (FnO) when attempting to change the company field after it has been initially set for an opportunity.
The customer is experiencing errors in Finance and Operations (FnO) when attempting to change the company field after it has been initially set for an opportunity.
Reason:
This may be related to limitations in the system that do not support cross-company data sharing, which can cause errors when the company field is modified after the initial entry.
This may be related to limitations in the system that do not support cross-company data sharing, which can cause errors when the company field is modified after the initial entry.
Resolution:
To address this with changing the company field, follow these steps: 1. Ensure that the company field is correctly set before the record is sent to Finance and Operations (FnO). 2. Implement validation rules to ensure the company field is correctly filled before saving the record. 3. Train users to understand the importance of setting the company field correctly the first time to reduce the likelihood of errors. 4. Create custom workflows that lock the company field after the initial save to prevent changes once the record is sent to FnO. 5. Implement error handling mechanisms to catch and address any issues arising from changes to the company field.
If changing the company field is a critical requirement, consider exploring custom solutions or workarounds, such as developing custom integration logic or using data migration tools for bulk updates.
To address this with changing the company field, follow these steps: 1. Ensure that the company field is correctly set before the record is sent to Finance and Operations (FnO). 2. Implement validation rules to ensure the company field is correctly filled before saving the record. 3. Train users to understand the importance of setting the company field correctly the first time to reduce the likelihood of errors. 4. Create custom workflows that lock the company field after the initial save to prevent changes once the record is sent to FnO. 5. Implement error handling mechanisms to catch and address any issues arising from changes to the company field.
If changing the company field is a critical requirement, consider exploring custom solutions or workarounds, such as developing custom integration logic or using data migration tools for bulk updates.