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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Special character in XML export

(0) ShareShare
ReportReport
Posted on by 536
Hi,

I have an entity with FieldX, when this string field has a weird character for a certain record, the export fails saying



 
 
But if this entity is part of composite entity, and i export the same exact record, the export doesn't fail, it succeeds and it accepts this weird character, why?

and when you open the file you will see the character like this
&#x2
 
<FieldX>bb
hii&#x2;000
bye

aa
</FieldX>

 
 

 
Categories:
I have the same question (0)
  • Diego Mancassola Profile Picture
    638 on at
    Hello, i have some case in the past similar than your, special chars found on XML generation, but always a problem against data. Seems something on string field value contains a special char, often a copy paste from word excel into a string field.
     
    Please check again the value on DB, i understand the same record exported in base entity works, but, in my option the problem is data.
     
    Provide us the details of entity you are using and details about the field and mapping
  • DELDYN Profile Picture
    536 on at
    Hi,

    i know it's a data issue and i can see the weird character in the field.
    My question was, why it errors for single entity but not for composite entity when exporting?
  • Diego Mancassola Profile Picture
    638 on at
    Hello, It may be related to the fact that the EDT or string definition used in the staging table of the single entity is not the same as the one used inside the composite entity.
     
    Can you check if the representation of the field is the same across two entities?
  • DELDYN Profile Picture
    536 on at
    Hi @Diego Mancassola

    But in the composite entity, we just drag the singular entity and put it inside it.

    So the entity and it's staging are not changed. it's just that we use this singular entity inside the composite entity (there is no staging for composite entity)

    So Entity1 has Stagin1

    and CompositeEntity, has Entity1 and other entities
  • Diego Mancassola Profile Picture
    638 on at
    Hello, at this point i've no idea.... can ben the composite entity does not perform some xml validation but  single entity do, and can be the reason why one fail and the other no.
     
    I don't know if other experts have any idea about it.
    Have you find out something new meanwhile?

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 583 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 378

#3
Diego Mancassola Profile Picture

Diego Mancassola 255

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans