M-Files Importer - traditional folder

Hi,

I have a specific use case for the M-Files Importer.

First question:
I need to import files along with their metadata and folder structure. I attempted to achieve this by loading folder and subfolder names into the "Traditional folder" (ID 34) property, using the VLI create new option. How can this be configured so that subsequent subfolders are treated as nested values within the value list?

Second question:
Is it possible to import a value list where the name and ID are identical (e.g., name: art1, ID: art1)?

Third question:
Does updating file metadata always require re-importing the file itself? If a duplicate is detected and only the metadata has changed, I would like to update just the metadata without re-importing the file.

BR

Parents
  • You can use Connection to External Sources -> File Sources to create folders and files in M-Files. Then you can export the list with ID's and update the metadata with Importer

    This will contradict with your second question as the files would have normal IDs as they get created by external source. But in theory, yes, you can map anything to External ID. Note that this will not change internal ID which will be assigned by M-Files

    And yes, you can use duplicate dedection of Importer to update metadata

Reply
  • You can use Connection to External Sources -> File Sources to create folders and files in M-Files. Then you can export the list with ID's and update the metadata with Importer

    This will contradict with your second question as the files would have normal IDs as they get created by external source. But in theory, yes, you can map anything to External ID. Note that this will not change internal ID which will be assigned by M-Files

    And yes, you can use duplicate dedection of Importer to update metadata

Children
No Data