I've got a scenario which I would like to create a media which that part can be done via MediaService but after that I need to create DAMP xml of the created media file and save that into a property of a document type that has a data type of DAMP which stores xml.
So is there any built-in function to call and generate the full DAMP XML ?
have find GetXML method in DigibizTree/DigibiMediaHelper.cs is that the right one?
I didn't know you store the DAMP data in a custom table. In that case it's always better to use the id instead of the xml because if you update the media item the xml in your custom table wouldn't get updated. That only happens if the xml is stored on a content node.
Upload media file and generate damp xml
Hi
I've got a scenario which I would like to create a media which that part can be done via MediaService but after that I need to create DAMP xml of the created media file and save that into a property of a document type that has a data type of DAMP which stores xml.
So is there any built-in function to call and generate the full DAMP XML ?
have find GetXML method in DigibizTree/DigibiMediaHelper.cs is that the right one?
Cheers
Ali
Hello,
In the DAMP 2.5 Samples package I also create media and set it on a DAMP property. You can find an example here (with the old API):
http://damp.codeplex.com/SourceControl/latest#DAMP.Samples/Installer.ascx.cs
Using GetXML in the DigibiMediaHelper.cs is the correct way.
Jeroen
Thanks Jeroen, I will give it a go and let you know.
Hello,
Did you get it working?
Jeroen
Long story short, I am using Damp data type with Dewd package for Custom table.
After a bit of trial and error we decided to store the ID of an image instead of XML in custom table.
Thanks for your help, I will give it a go as soon as I get a chance.
Cheers
Ali
I didn't know you store the DAMP data in a custom table. In that case it's always better to use the id instead of the xml because if you update the media item the xml in your custom table wouldn't get updated. That only happens if the xml is stored on a content node.
Jeroen
is working on a reply...