Share
Report
2Hi,
I am working on an extension where we have a custom field in Purch. Rcpt. Line Table Extension:
field(67; "Vendor Shipment No."; Code[35])
In the newer BC version, Microsoft has introduced the same field with a different ID:
field(5797; "Vendor Shipment No."; Code[35])
Because both fields have the same name, I am getting AL0887 during the upgrade.
AL0887: A member of type Field named 'Vendor Shipment No.' conflicts with a similarly named member 'Vendor Shipment No.' of Table Purch. Rcpt. Line. Both will have the same database name 'Table'.
The main concern is that Field 67 already contains production data, and this value is also flowing to the other documents.
I checked Microsoft's documentation for PTE merge conflicts, and their suggested approach is to backup the data, uninstall the extension with "Delete extension data and schema", remove the conflicting field, and then restore the data:
Microsoft – Upgrading per-tenant extensions that conflict with other extensions
However, I have 5–6 companies in the environment, and the PTE has around 55 custom tables and 43 table extensions with a lot of data. Because of this, the deletion and backup/restore approach seems quite complicated and risky, and I would prefer not to use the deletion approach if there is another supported option.
So I wanted to ask:
- Is there any other supported way to resolve this conflict and migrate Field 67 + its existing data to Microsoft's Field 5797 without deleting the extension data/schema?
- Is there a recommended approach for handling this when there are multiple companies and a large amount of PTE data?
- If the deletion approach is the only supported option, is there a safer/easier way to handle the backup and restoration for all companies and tables?
I will test the solution in a production-copy sandbox first.
If anyone has dealt with a similar issue, please share your experience or any suggestions. It would be really helpful.
Thanks,
Ankit
All responses (
Answers (
