TANE kuid's in session

[celje]

My session is on DLS, so i must made the clone to edit session and made changes. Clone has new kuid number, what to do that session will have the original kuid with :1, when i will upload changes. I tried type the original kuid with :1 in config, but CM refuse to commit it

 

[oknotsen]

Did you also change "KUID:" to "KUID2:"?

 

[BuilderBob]

My session is on DLS, so i must made the clone to edit session and made changes. Clone has new kuid number, what to do that session will have the original kuid with :1, when i will upload changes. I tried type the original kuid with :1 in config, but CM refuse to commit it

You can't Commit (or Submit) if the KUID is changed. You must 'Import Content Folder...'. A new asset with the new KUID will be created when the folder is imported.

 

[celje]

Did you also change "KUID:" to "KUID2:"?

Original has kuid without 2, so i used kuid:xxxxxx:xxxxxx:1


BuilderBob

What's about Create new version? i wish that upgraded session automatic replace the original one.

 

[SailorDan]

Original has kuid without 2, so i used kuid:xxxxxx:xxxxxx:1
What's about Create new version?

That won't work. The new kuid must be <kuid2:xxxxxx:xxxxxx:1>

A new version is a new asset.

 

[BuilderBob]

What's about Create new version?

This is what you said: "I tried type the original kuid with :1 in config, but CM refuse to commit it"

If you change the KUID then you must import the folder.

If you used 'Create New Version' then there was no need to change the KUID.

 

[celje]

I apologize, I'm the clumsy old one, do I understand correct. If i type in config <kuid2:xxxxxx:xxxxxx:1> will this automatic replace the original version kuid:xxxxxx:xxxxxx, which will become obsolete

 

[BuilderBob]

I apologize, I'm the clumsy old one, do I understand correct. If i type in config <kuid2:xxxxxx:xxxxxx:1> will this automatic replace the original version kuid:xxxxxx:xxxxxx, which will become obsolete

If you change the KUID and import the folder, then you are creating a new asset. If you change the KUID in the way you describe then that new asset will obsolete the original <kuid:xxxxxx:xxxxxx>. The original is not removed, but any route that uses that original asset will now use the new one.

 

[celje]

Thank you very much to all

 

[trev999]

celje - It is not necessary to change the kuid in the config file. There is a facility to upgrade your own assets:

In Content Manager, select the asset with the mouse.
At the top left of the window, find the Content tab and click it.
The 7th item is: Create New Version. Click that. A window reports that a new version has been created.
Now select the filter: Open for Editing. A New Asset is displayed with the updated kuid.
Select this asset and click Submit Edits.
Select filter: My Content and you will find your asset is updated.


To N3V: Is there any reason why the update process does not automatically submit the new asset? That would save several of the steps needed above to make the update immediately visible. There is no point in giving the new asset a name other than that of the original asset, thus causing the user to have to hunt for the updated one and submit it himself.

 

[celje]

Thank you Trev
It's correct if you have the same kuid number. But with clone session you get the new, different kuid number, as original session has.

 

[trev999]

celje - What you say is true if you Clone your session but you should use Create New Version rather than cloning it. Then you will have the same kuid with a new version number.

Regards - Trev