Edit

Share via

ExperienceID

  • Article

MBAE deprecation warning

Important

Starting in Windows 10, version 1803, the MBAE app experience is replaced by an MO UWP app. For more information about MO UWP apps, see UWP mobile broadband apps.

The ExperienceID element specifies a GUID representing the device experience. This GUID is used to group one or more metadata packages for the same device identifiers independent of the packages’ locale.

In Windows 8, Windows 8.1, and Windows 10 it is also used to link the device metadata to a device app that can be automatically acquired when the device is first connected. A device app specifies one or more ExperienceID elements in a StoreManifest.XML file in the app submission package. Each of these ExperienceID GUIDs corresponds to the ExperienceID element of a device metadata package. After the StoreManifest.xml file has been submitted, the device app can then be distributed to one or more device models, if the ExperienceID in a device’s metadata is also specified in the device apps StoreManifest file.

Usage

<ExperienceID>
  text
</ExperienceID>

Attributes

There are no attributes.

Text value

A value formatted as a GUIDType XML simple type.

Child elements

There are no child elements.

Parent elements

Element Description

Relationships

The Relationships element specifies data that is used to track a device metadata package within the device metadata cache.

XSD

<xs:element name="ExperienceID" type="tns:GUIDType" minOccurs="0" />

Remarks

In Windows 8.1 and Windows 10, the ExperienceID is created by the Service Metadata Wizard on the Windows Dev Center Dashboard.

In Windows 8 the ExperienceID can be specified by the service metadata developer, or automatically generated and added to the service metadata using the Device Metadata Authoring Wizard. If the ExperienceID is not specified in the service metadata package, the Windows Dev Center Dashboard creates a GUID and updates the ExperienceID element within the metadata package when the mobile network operator or mobile virtual network operator submits the service metadata package.