DBohner-(db)
Legendary Poster
Howdy,
In 9.x, we have the BSFN B01RS056 - which allows us to export a version's Data Selection. It has it limitations, mostly in parameter sizing and abandoned logic (limiting the DS String to 95 characters does not catch those 300 MCUs in the "list"). The function appears to export the version to XML, then cache the Data Selection - allowing you to fetch back the DS from the cache. It works. Copying the function and extending the lengths of the structures works, too...
Because the function uses the XRCS (Xerces) api's - I don't believe that the same can be replicated into XE (I am making an assumption...).
Basically, the function exports the spec to XML, reads the XML Data Selection into Cache - then allows you to fetch the DS Rows from Cache in a legible format. In my exercise, I read each row of data selection and concatenated into a longer string - creating a single Data Selection string for each Version. This 'export' can be run in each environment - then Beyond Compare can be used to validate the similarities / differences per version (very quickly)....
That said....:
- is there a good way to compare Version Data Selection between XE and Upgraded Environments?
- what, if any, tricks have you guys found to validate Version Data Selection during a significant upgrade.
Thoughts?
(db)
In 9.x, we have the BSFN B01RS056 - which allows us to export a version's Data Selection. It has it limitations, mostly in parameter sizing and abandoned logic (limiting the DS String to 95 characters does not catch those 300 MCUs in the "list"). The function appears to export the version to XML, then cache the Data Selection - allowing you to fetch back the DS from the cache. It works. Copying the function and extending the lengths of the structures works, too...
Because the function uses the XRCS (Xerces) api's - I don't believe that the same can be replicated into XE (I am making an assumption...).
Basically, the function exports the spec to XML, reads the XML Data Selection into Cache - then allows you to fetch the DS Rows from Cache in a legible format. In my exercise, I read each row of data selection and concatenated into a longer string - creating a single Data Selection string for each Version. This 'export' can be run in each environment - then Beyond Compare can be used to validate the similarities / differences per version (very quickly)....
That said....:
- is there a good way to compare Version Data Selection between XE and Upgraded Environments?
- what, if any, tricks have you guys found to validate Version Data Selection during a significant upgrade.
Thoughts?
(db)