A couple of time I have accidentally loaded .cdp files of TRS19 saved routes and sessions, with build 4.6, into TANE SP3. CM in both programs looks identical so this is probably an easy error to make.
On these occasions, the .cdps have imported successfully, 0 warnings and 0 errors, but appear in CM with a grey font and have the status "Faulty, missing dependencies". In the route and session I have used the dependencies are all on the DLS and are present in both TANE and TRS19 so they are probably not actually missing (although I understand that the baseboard grid in TRS19 is a PBX texture not available in TANE so that may explain the status).
My point is that TRS19 assets with build 4.6 should not load into TANE SP2/SP3 which has, I believe, a maximum build number of 4.5. Is this a bug or a feature?
I suspect that some users may be fooled by this into thinking that the asset is faulty or actually missing assets and they may possibly start posting questions about where they can find the mysterious "missing" dependencies.
On these occasions, the .cdps have imported successfully, 0 warnings and 0 errors, but appear in CM with a grey font and have the status "Faulty, missing dependencies". In the route and session I have used the dependencies are all on the DLS and are present in both TANE and TRS19 so they are probably not actually missing (although I understand that the baseboard grid in TRS19 is a PBX texture not available in TANE so that may explain the status).
My point is that TRS19 assets with build 4.6 should not load into TANE SP2/SP3 which has, I believe, a maximum build number of 4.5. Is this a bug or a feature?
I suspect that some users may be fooled by this into thinking that the asset is faulty or actually missing assets and they may possibly start posting questions about where they can find the mysterious "missing" dependencies.