Hi ​@K.K

one possibility is that this happens with the Document type definition for the ZIP files in your basic data setup. if the ZIP files are set up as VIEW then there will be two records for both original and view.

 

Below is what's mentioned in our documentation.
“
Original - The document file is an original. When checking in a file, the system will accept file types that are registered as original or view. If a view type file is selected for checking in, two file references will be created in Document Revision/File Refs. tab for the same file, but with different document types, original and view.

View - The document file is a view-only copy. Typically, this document type is used for an Acrobat PDF or an AutoCAD DWF file. When checking in a file, the system looks for file types registered as View Copy with the same name as the original, but with a view copy extension.”

Hi,

When attaching a zip file, the system sometimes creates two files: "ORIGINAL" and "VIEW" in the "FILE REFS" tab in the document revision:

The parameterization looks like this:

A duplicate entry is visible in the edm_file_tab table.

Does anyone know why the system creates "ORIGINAL" in most, and sometimes ‘ORIGINAL’ and ‘VIEW’?

Best regards

Was there also a PDF file in the same folder where you checked in the Zip file from? That's the only thing that can explain that, the way I see it.

Hi ​@Asitha Rajapaksha,

Thank you for the information, but here we have a situation where the zip is original and despite this the pdf file was created as VIEW.

Best regards

Hi ​@Mathias Dahl,

Yes, they were in the same folder. However, on the next attempt, the situation didn't repeat itself.

Best regards

What happened to you is what should happen. That is, the view copy (the PDF file in this case) will be uploaded alongside the original file (Zip file in this case).

I don't believe that it happens only sometimes, if you do the same thing again. Can you show us with some screenshots?

Unfortunately I don’t have any screenshots. The described situation occurs at our client. That is why I created a query to find a potential cause, because I didn't notice similar behavior.

​@K.K 

Okay, thanks. Well, we have explain how it works, how it should work. If the customer see something different, and can recreate the problem reliably, ask them to file a support case with us so that we can look into it.

Thanks!