Power Platform Community Forum Thread Details

I've created a pcf component having in the manifest the following resources:

<resources>
<code path="index.ts" order="1"/> 
<css path="css/TS_DataSetGrid.css" order="1" />
<img path="imgs/users.svg" />
<resx path="strings/TSDataSetGrid.1033.resx" version="1.0.0" />
<css path="css/font-awesome/font-awesome.css" order="1" /> 
<css path="css/font-awesome/fontawesome_webfont.eot" order="2" /> 
<css path="css/font-awesome/fontawesome_webfont.svg" order="2" /> 
<css path="css/font-awesome/fontawesome_webfont.ttf" order="2" /> 
<css path="css/font-awesome/fontawesome_webfont.woff" order="2" /> 
<css path="css/font-awesome/fontawesome_webfont.woff2" order="2" /> 
</resources>

This worked before upgrading the pac tool. Now I cannot import the solution in my system anymore.
When importing the solution I get the error:

09:55:22.22 Solution BirDiaPresetterSolution BirDiaPresetterSolution Failure Import Solution Failed: CustomControl with name failed to import with error: Part URI is not valid per rules defined in the Open Packaging Conventions specification.

09:55:22.32 Manifest.xml Failure 0x80160000 CustomControl with name failed to import with error: Part URI is not valid per rules defined in the Open Packaging Conventions specification.

But it works if I use this resources in my manifest file (no font-awesome subfolder this time):

<resources>
<code path="index.ts" order="1"/> 
<css path="css/TS_DataSetGrid.css" order="1" />
<img path="imgs/users.svg" />
<resx path="strings/TSDataSetGrid.1033.resx" version="1.0.0" />
<css path="css/font-awesome.css" order="1" /> 
<css path="css/fontawesome_webfont.eot" order="2" /> 
<css path="css/fontawesome_webfont.svg" order="2" /> 
<css path="css/fontawesome_webfont.ttf" order="2" /> 
<css path="css/fontawesome_webfont.woff" order="2" /> 
<css path="css/fontawesome_webfont.woff2" order="2" /> 
</resources>

I've checked if the problem is the "-" in the "font-awesome" folder, but that's not the issue.

It seems to me to be only a problem of replacement of "/" to "\" in the manifest, because tha path contains both "/" and "\".

Just in case it helps, the ControlManifest.xml inside my solution package looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<manifest>
 <control namespace="BirDiaPresetter" constructor="BirDiaPresetter" version="0.0.15" display-name-key="BirDiaPresetter_Display_Key" description-key="BirDiaPresetter_Desc_Key" control-type="standard" api-version="1.1.0">
 <data-set name="dataSetGrid" display-name-key="DataSetGridProperty_Display_Key"/>
 <resources>
 <code path="bundle.js" order="1"/>
 <css path="css/TS_DataSetGrid.css" order="1"/>
 <css path="css/fontawesome\font-awesome.css" order="1"/>
 <css path="css/fontawesome\fontawesome_webfont.eot" order="2"/>
 <css path="css/fontawesome\fontawesome_webfont.svg" order="2"/>
 <css path="css/fontawesome\fontawesome_webfont.ttf" order="2"/>
 <css path="css/fontawesome\fontawesome_webfont.woff" order="2"/>
 <css path="css/fontawesome\fontawesome_webfont.woff2" order="2"/>
 <img path="imgs/users.svg"/>
 <resx path="strings/TSDataSetGrid.1033.resx" version="1.0.0"/>
 </resources>
 <built-by name="pac" version="0.2.71"/>
 </control>
</manifest>

Just in case the deeper subfolder-structure shouldn't be supported by design, please report the problem while building the solution, because it took hours to find out the problem while importing the solution.

Best regards,

Diana

Categories:

Power Apps Pro Dev & ISV