Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

The following XML example sets the hierarchy for a set of folders by using FolderHierarchysettings.

Note:
The folder hierarchy settings need to be sent to the device after the initial sync has already been performed, otherwise the folder hierarchy is not yet on the device and the provisioning xml will not do anything.

Code Example

Copy Code 
<characteristic type="Sync">
   <characteristic type="FolderHierarchy">
	<characteristic type="Inbox">
		 <characteristic type="Meeting Notes">
			<parm name="SyncEnabled" value="1"/>
		 </characteristic>
		 <characteristic type="Project Folders">
			<characteristic type="urgent">
			 <parm name="SyncEnabled" value="1"/>
			</characteristic>
			<characteristic type="Contacts & Associates">
			 <parm name="SyncEnabled" value="1"/>
			</characteristic>
		 </characteristic>
	</characteristic>
   </characteristic>
</characteristic>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.