While creating ECL multimedia Components using the Core Service, we've noticed a difference between creating them via the Core Service and creating them within the SDL Web UI.
- Creating them in the UI displays the key
{tcmid}
AND ECL Media{eclidfile}
- Creating them via the Core Service does not display the ECL Media
{eclidfile}
- However, both in the source of the Components look to be correct
Manually Created in UI
<MediaBlock xmlns="http://ecm.disney.com/wdpr/MediaBlock">
<key xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:type="simple" xlink:href="tcm:401-124373"
xlink:title="finderStandardThumb"></key>
<media xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:type="simple"
xlink:href="ecl:401-mb-200466156-fil-file"
xlink:title="star-tours-gallery06-sq.jpg"></media>
</MediaBlock>
tcmids do not match screenshots
Created via Core Services
<MediaBlock xmlns="http://ecm.disney.com/wdpr/MediaBlock">
<key xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:type="simple" xlink:href="tcm:401-124373"
xlink:title="finderStandardThumb"></key>
<media xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:type="simple" xlink:href="ecl:401-mb-200466156-fil-file"
xlink:title="star-tours-gallery06-sq.jpg"></media>
</MediaBlock>
tcmids do not match screenshots
So the issue is when we preview in TCM or publish the Component with media on it, it does not expose the ECL Media node.
Is there anything that is stored in a different place? AppData
?
UPDATE
We are importing ECL and creating (content) Component relationships, and from that we are missing the Media ECL ID as shown above in 2nd screenshot. If its created manually in the UI everything is good, but through the Core Service something is missing.
We are just trying to figure
- How to access that info that is missing
ecl:0-mb-200450850-fil-file
- Or, if this is a defect? Since that is how we grab the ECL metadata from DAM external system
ecl:0-mb-200450850-fil-file
#2. Or, if this is a defect ? Since that is how we grab the ecl metadata from DAM external system