If a user encounters issues on a particular Project where Relative File Path is empty, then this will affect the all locations overlay as the duplicate file path is not being populated.
To resolve the issue, try ingesting the same file in a test project and check if the relative path is populating / not populating.
Then check if the ingestion engine is a fallback or legacy. Then run the below query in the Project Database:
SELECT * FROM tbl_pj_ProjectSetting WHERE [KEY]='INGESTION_ENGINE_TYPE'
For file information see the results of the query below:
SELECT * FROM tbl_ex_FileInfo WHERE fileid=<parentfileid>
If fallback engine, then:
SELECT I.* FROM tbl_jb_Ingestion I, tbl_ex_FileInfo f
WHERE f.FileId=I.FILEID and f.fileid=<parentfileid>
If legacy engine, then:
SELECT I.* FROM tbl_jb_IngestionFileExpansion I, tbl_ex_FileInfo F
WHERE F.GroupId=I.GroupId AND F.FileId=<parentfileid>
If issues persist, check a sample document provided by the user, and if the issue seems to be due to moving document to different file.
- See if the process of moving the document does not work when moving document to top level archive file.
- Verify if it works only moving document to parent and its child document.
To fix that persistent issue follow the steps below (note this fix is only for those files with issues):
- Backup project database.
- Execute the query below in the project database.
update tbl_ex_FileInfo set IsParent=1,IsEmbedded=0,GroupId=FileId WHERE FileId IN (<parentfileid1, parentfileid2, parentfileidn, ...>)
EXEC sp_su_SetMediaSummary 41,1,1,1,1
Comments
0 comments
Please sign in to leave a comment.