You’re offline. This is a read only version of the page.
Hi Team,
We have developed a PCF control for a single line of text and we use the latest PowerApps Component Framework (Version: 0.2.899.1). We do not get the WebAPI and Utility feature inside context. All values inside context of WebAPI and Utility feature are nulls. We add below lines in ControlManifest.Input.xml but no success, we get below error while importing the solution as below:
<feature-usage>
<uses-feature name="Utility" required="true" />
<uses-feature name="WebAPI" required="true" />
</feature-usage>
Error: Import Solution Failed: CustomControl with name failed to import with error: The import manifest file is invalid. XSD validation failed with the following error: 'The import manifest file is invalid. XSD validation failed with the following error: 'The element 'control' has invalid child element 'feature-usage'. List of possible elements expected: 'data-set, built-by, modes, child, type-group, common-property, property, groups, dependencies, property-dependencies, event, subscribed-functionalities, resources, AvailableOn'.'."'."
Thank You.
Hi,
It seems Lookup.Simple is not accepted by PCF cli.
of-type="Lookup.Simple"
I have received the following error:
[pcf-1014] [Error] Manifest validation error: instance.manifest.control[0].property[0].$.of-type is not one of enum values: Whole.None,TwoOptions,DateAndTime.DateOnly,DateAndTime.DateAndTime,Decimal,Enum,FP,Multiple,Currency,OptionSet,SingleLine.Email,SingleLine.Text,SingleLine.TextArea,SingleLine.URL,SingleLine.Ticker,SingleLine.Phone
Any idea?
Thanks in advance
@sheldoncopper73 It should be resolved now; a fix for the known issue made it everywhere on Friday. If it's still not working for you, can you post the server version, client version, and session ID you have in the environment where it's not working? To find it, open a Unified Interface app, click the gear icon in the upper right next to your name, click About, and copy the information there.
EDIT: One more thing: can you post your current ControlManifest.Input.xml file? If at some point you removed this section, you'll need to put it back.
<feature-usage> <uses-feature name="Utility" required="true" /> <uses-feature name="WebAPI" required="true" /> </feature-usage>
Hey @GregHurlmanMSFT any updates regarding context bug we checked it today but it is still unresolved.
Thank you for you quick response, Greg.
I extracted the zip file, removed apiversion attribute, increased the version number and compressed it to a zip file. After deploying it is working perfectly.
Thanks you again for the workaround.
All, I apologize for this -- there was an issue that we had already caught, but had not made it out to all of our production servers yet. The fix should be deployed everywhere on July 27th.
In the meantime, if you want to work around the issue you can remove the apiVersion attribute from your component's compiled ControlManifest.xml file. Please note that this attribute will need to be in place for production use upon release, but it will work without it for now.
@JoCas @sheldoncopper73 I've been able to repro your exact problem, and have created a bug to get the issue resolved; thanks for bringing it to our attention!
OK, thanks -- I'm going to try to repro in a matching environment; will follow up.
#1
WarrenBelz
83
Most Valuable Professional
#2
mmbr1606
55
Super User 2025 Season 1
#3
stampcoin
50
Share
Report
All responses (
Answers (