Mx6 to Mx7 migration: How to solve the filedocuments without a specialization

0
In Mx6 you could set the security of filedocuments in the project security. In Mx7 this is deprecated as you should set the security on the specialization of filedocuments. But how to check the loose ends? We already use specializations on filedocuments. But some projects are 5 years old and I am not 100 procent sure this is / has always be done. Is there an easy way to retrieve all the filedocuments that have no specialization? Because after the migration I am not allowed to retrieve those objects again, so before the upgrade I should either remove them or copy them to the right specialization. The only way I can think of now is to retrieve all the file documents and substract each specialization but there must be a simpeler sollution I think. Regards, Ronald  
asked
2 answers
0

If you have access to the database, you could inspect the system$filedocument table to verify:

SELECT * FROM system$filedocument WHERE submetaobjectname='System.FileDocument';

answered
0

Sounds like a job for the Mendix SDK.

answered