web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Dynamics 365 v.9 - 0x80040203 Expected non-empty string. Parameter name: SiteMapName

(4) ShareShare
ReportReport
Posted on by 5

Hi!

If you have to import APP in Dynamics Customer Engagment v9.0 and will find this error "0x80040203 Expected non-empty string. Parameter name: SiteMapName" is because when you exported your solution in the customizations.xml is missing the node XML <SiteMapName> after every SiteMapUniqueName in the AppModuleSiteMap.

You have to add this node in every AppModuleSiteMap. 

This is an example:

      <AppModuleSiteMaps>

<AppModuleSiteMap>
      <SiteMapUniqueName>bd3c391f1a7c48818b7841cb8dc9a1cc</SiteMapUniqueName>
       <SiteMapName>Dynamics 365 Mobile – personalizzato</SiteMapName> NODE TO ADD!!

Hope this is useful for someone :)

Alberto

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Hi Alberto,

    I am facing the same issue concerning our own FieldService APP.

    Just to inform you all:

    - Adding the node to the solution (managed) and importing it to the destination-system worked

    - Adding the node to the solution (unmanaged) and reimporting it to the source-system doesn't worked for me

    Can you reproduce this behaviour Alberto?

    Best Regards,

    Lukas

  • Verified answer
    Henrik H Profile Picture
    90 on at

    Thanks for posting this, Alberto. I experienced the same error when moving a solution between source and target environments that were recently upgraded to v9. Both environments are running version 1710 (9.0.2.1725).

    I can confirm that your fix makes this work. To further elaborate, I experienced the following behavior:

    First, I applied your fix by adding a <SiteMapName>-tag to the affected AppModuleSiteMap (the importlog.xml from a failed import shows which AppModuleSiteMap has the problem):

    <AppModuleSiteMap>
        <SiteMapUniqueName>prefix_name</SiteMapUniqueName>
        <SiteMapName>My Human Readable Name</SiteMapName>
        ...
    </AppModuleSiteMap>

    After importing this solution to my source environment and re-exporting the same solution, I ended up with the following XML (where the SiteMapName-tag has disappeared but instead been replaced with a LocalizedName-tag):

    <AppModuleSiteMap>
        <SiteMapUniqueName>prefix_name</SiteMapUniqueName>
        <LocalizedNames>
            <LocalizedName description="My Human Readable Name" languagecode="1033" />
        </LocalizedNames>
    </AppModuleSiteMap>

    The solution can then subsequently be imported to the target environment without issues.

    Since the issue does not occur for me any more, I have not dug into whether it would be sufficient to directly add the LocalizedName-tag (or if it would be possible to do so from the UI).

  • julians Profile Picture
    612 Moderator on at

    Yes just had this problem after upgrading to 9.0 and adding in SiteMapName node has fixed it

    Thanks

  • Alberto Valente Profile Picture
    5 on at

    Henrik, Thank you for your post.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans