Skip to content

Latest commit

 

History

History
32 lines (23 loc) · 2.97 KB

provisionfromxmldocumentresults_provisionresultsxml.md

File metadata and controls

32 lines (23 loc) · 2.97 KB
-api-id -api-type -api-device-family-note
P:Windows.Networking.NetworkOperators.ProvisionFromXmlDocumentResults.ProvisionResultsXml
winrt property
xbox

Windows.Networking.NetworkOperators.ProvisionFromXmlDocumentResults.ProvisionResultsXml

-description

Indicates which elements in the provisioning profile could not be successfully provisioned.

Note

This functionality is available only to mobile operator apps and UWP apps given privileged access by mobile network operators.

If you want to use this API and publish your app to the Microsoft Store, then you'll need special approval. For more information, see the Restricted capabilities section in the App capability declarations topic.

-property-value

An instance of ResultsSchema that indicates which elements in the provisioning profile could not be successfully provisioned.

-remarks

Calling ProvisionResultsXml when no provisioning file has been submitted will result in an error. When the file was submitted, but not processed due to signature issues, only the Signature element of ResultsSchema will be present. If ProvisionFromXmlDocumentAsync returned an error, ResultsSchema will indicate “Failure” at the file level in the CarrierProvisioningResult element, with the error code specified. If the file was valid, but errors occurred while acting on it, ResultsSchema will coalesce errors, listing the error code at the highest level at which it applies to all sections underneath. If errors are coalesced to a higher level, the lower levels are not included. For example, if all WLAN profiles failed for the same reason, this reason will be shown as an attribute of the WLANProfiles node. If different profiles failed for different reasons, then each profile will be enumerated and indicate success or failure with the error code specified. In cases where multiple adapters are present, a success on any adapter should be represented as success, even if the profile failed to apply to other adapters. If a profile failed to apply to all adapters, ResultsSchema will contain at least one of the error codes, but will not enumerate all errors which occurred on various adapters.

-examples

-see-also

-capabilities

cellularDeviceIdentity, cellularDeviceControl