Recommended approach to export primary and secondary content for all WTDocument revisions
windchill 13.0.2
Hi All,
We have a requirement to perform a one-time export of WTDocuments along with their primary and secondary content for all revisions.
Currently, our utility takes an input date and identifies the closest/relevant WTDocument revision based on that date, then downloads the primary and secondary content associated with that revision.
For the new one-time export approach, we are considering exporting:
- All WTDocuments
- All revisions of each WTDocument
- Primary content for each revision
- Secondary content/attachments for each revision
However, since each WTDocument can have multiple revisions and associated content, exporting the content for all revisions could result in a very large volume of data.
What is the recommended approach in Windchill for handling this type of bulk export?
Is there any standard or recommended API, utility, or approach for efficiently exporting primary and secondary content across all revisions of WTDocuments?
Also, are there any recommended strategies to handle the large volume of content during a one-time export/data migration?
Can we achieve this requirement without using Windchill Bulk Migrator (WBM)?
Any suggestions or similar implementation experiences would be helpful.
Thanks.
We have tried using a utility to export the primary and secondary content for all WTDocument revisions, but it is taking a significant amount of time due to the large volume of data.
Our organization has a data migration requirement to perform a one-time export of WTDocuments & CAD Object, including the primary and secondary content for all revisions. Since the volume of documents, revisions, and associated content is large, the current utility is taking considerable time. We are looking for an efficient and recommended approach to perform this export.
The current utility is taking a significant amount of time to export the primary and secondary content for all revisions of WTDocuments due to the large volume of data. This is impacting the overall data migration timeline and efficiency. We are looking for a more efficient approach to handle the bulk export.