Hi @satish_puli,
As far as I remember, the crx:///
protocol is no longer supported for security and architectural reasons. Cloud Service utilizes Asset APIs/CDA (Content Delivery API) for exposing DAM assets, and direct repository calls like crx:///
aren’t allowed.
The image field in your XDP cannot resolve the crx:///content/dam/myproject/images/logos/xyz.jpg
reference, so the logo never loads. To fix the issue, Instead of crx:///
, construct an HTTP(S) URL pointing to the published asset (e.g., via Asset Share or directly from DAM's public URL):
var baseUrl = "https://author-pXXXX-eYYYY.adobeaemcloud.com/content/dam/myproject/images/logos/";
var imageName = xfa.resolveNode("xfa.record.ImageName");
if (imageName !== null) {
this.logo.value.image.href = baseUrl + imageName.value + ".jpg";
}
You can also choose author or publish based on where the Output Service runs and asset availability. You can include the base64-encoded image in the XML if really dynamic, but it’s not efficient for large or many images.
Thanks
Pranay