We are looking for a way to import documents from a shared folder or local c drive into IFS cloud document management.
Tried using Cloud File storage Migration Tool (FS Mig Tool) but seems it is most suitable for environment-to-environment migration.
The documents need to be attached to the corresponding business object screens under the attachment section. Importing them manually one by one would be time consuming, so we are looking for a batch import approach.
Any suggestions would be greatly appreciated.
Thank You!
Page 1 / 1
In the past I’ve done it via migration jobs. Initially the meta data was loaded (Doc Revision related info), Seperately the document files (CLOB / BLOB) was imported and the object connection was made. NOTE: in that instance the document files were stored in the database.
I haven’t used the below tool, but seems it can be used to load LOB files to the DB.
once it is loaded to the database you will have to transfer it across to Document Revs.
In Cloud, it would make sense to have the document files stored in the Azure File Storage (if hosted in Azure servers).
In Cloud, you can already import several files at once via "New Document" in the standard version and don't have to do it one by one. Simply drag in all the files you want to attach. It is important to note that they must all have the same document class for each mass import.
Thank you for your response!
Yes, I am aware that multiple files can be drag-dropped at once.
However, my requirement is a bit different, I need to attach multiple files to different business objects, not all to a single one.
For example, I have around 100 Inventory parts, and each part has one or two documents that need to be attached. All the documents (PDF files) are in shared folder, and I am looking for a way to upload or link them in bulk to their respective parts without opening each part one by one.
@snehaG Migration job is the way to go I think
As @malik.sally has already written, you only have a migration job or, as we usually do when transferring technical documents from CAD or external PDM, a corresponding interface. Ideally, the affiliation to the part/version should be evident from the file name of the document, which simplifies the conversion.
