Hi experts,
I have a table in which field A, field B and RecId are under an index. The idea of adding RecId to index is purely to give the index as primary index to the table for the unique indexing. This is a technical mistake that was did and released to the customer.
Now, today the customer has more data in that table. And they tried to update few fields through DMF and it failed cause we don't have a unique Id that customer could specify to update a certain record.
Now the work around in ISV part is, we introduced a new field which is a line number. Now this is unique. But the new field needs data to be updated to act as unique field. We did develop a periodic job to update the new field.
This is the way we planned to release it.
Release 1 : Release the new field + periodic job to update the new field value in one release. But without adding the new field as unique index (The index changes are not given so that the synchronization doesn't fail since LineNum (new field) is empty as of now.
Release 2 : Release the indexing changes.
But as second thought, we are in process of analysing whether there is any way to release this as a single release. Can anyone advice if there is any way to do that?
Regards,
John
141
Share
Report
All responses (
Answers (
