Closed srasp closed 4 years ago
@srasp Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.
@divyaswarnkar, could you please respond?
Do you any news or updates to my question?
@srasp Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.
@divyaswarnkar, could you please respond?
Hi, do you have any news on that? Thank you
@srasp yes, that should work. You would have to upload all the schemas in the Integration Account.
@srasp yes, that should work. You would have to upload all the schemas in the Integration Account.
Thank you for your reply. This is what I already did. I tried it with the map name in the xsl:include/xsl:import as well as the URL of the map. Both didn’t work. Do you have an example.
Best regards Seb
@srasp you can check these out https://divyawestusstorage.blob.core.windows.net/schemas/IDoc.ORDERS05.700.3.xsd https://divyawestusstorage.blob.core.windows.net/schemas/IDocOperation.ORDERS05.700.3.Send.xsd
Thank you for the example. You have sent me a XSD, which imports another XSD and not a XSLT example. The xsl-include statement uses the attribute href to reference the stylesheet document which should be included.
I tried the following:
Unfortunately, it doesn't work. I always get the following message: An error occurred while transforming the given input with the provided map. Details: 'net.sf.saxon.trans.XPathException: Could not find file 'D:\\Windows\\system32\\nameOfTheMapToInclude'.'.\"
BTW: The XSL to include is valid.
Thank you Seb
@divyaswarnkar: Is there anything that we need to add to the doc?
@srasp sorry about the confusion. We don’t support referring another XSLT from the integration account. However you can have import using URL for any publicly available XSLT like from a blob etc. Let me know if you need more information.
@srasp sorry about the confusion. We don’t support referring another XSLT from the integration account. However you can have import using URL for any publicly available XSLT like from a blob etc. Let me know if you need more information.
Thank you! I was wondering if you can share an example with me.
@divyaswarnkar: Is there anything that we need to add to the doc?
I recommend to add a note to the doc, that nested XSLTs (xsl:imports/xsl:includes of stylesheets) within an integration account are currently not supported. Only external XSLTs from another server. Actually, this is something, I wish to get improved in Logic Apps and the “XML Transform” component in the near future, because imports/includes give the ability to implement cleaner, more flexible and less redundant XSLTs.
Thank you Seb
@srasp sorry about the confusion. We don’t support referring another XSLT from the integration account. However you can have import using URL for any publicly available XSLT like from a blob etc. Let me know if you need more information.
Thank you! I was wondering if you can share an example with me or add something to the documentation. Actually, this was my initial request.
@divyaswarnkar, any feedback on @srasp's doc update suggestion?
@divyaswarnkar, any feedback on @srasp's doc update suggestion?
Sorry, I have overseen your reply. I already mentioned it above “I recommend to add a note to the doc, that nested XSLTs (xsl:imports/xsl:includes of stylesheets) within an integration account are currently not supported. Only external XSLTs from another server. “
Actually, this is something, I wish to get improved in Logic Apps and the “XML Transform” component in the near future, because imports/includes give the ability to implement cleaner, more flexible and less redundant XSLTs.
Hi, I am missing the information about nested XML stylesheets. If it is possible to include (xsl:import/xsl:include) a XSLT/map in another XSLT/map.
Thank you Seb
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.