Skip to main content

Notifications

Finance | Project Operations, Human Resources, ...
Unanswered

"Invalid character value for cast specification"

(0) ShareShare
ReportReport
Posted on by 465

I'm getting this error when the entity exports using recurring integration:

An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0".  Description: "Invalid character value for cast specification".

  • D365FO user Profile Picture
    D365FO user 465 on at
    RE: "Invalid character value for cast specification"

    Hi Andre,

    I'm not the one who did the refresh but i'll ask.

    First, how do we sync uat DB?

    2nd, what do u mean by incorrect references or not available references can you please explain?

    3rd, i looked at product version and platform version for both UAT and Prod and they are indeed different..so what do u think happened exactly?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,965 Super User 2025 Season 1 on at
    RE: "Invalid character value for cast specification"

    Hi D365FO user,

    Did you synchronize the database after the refresh from live? There might be some references incorrect or not available yet. Namely in case the environments are not having the same application version or customizations.

  • D365FO user Profile Picture
    D365FO user 465 on at
    RE: "Invalid character value for cast specification"

    Hi Andre,

    This is a customized entity that gets exported via recurring integration. (Change tracking is enabled)

    It happens in UAT and it started happening after a refresh was made to copy data from live to UAT. -- it was woking before

    It seems it's happening to more than on customized entity where recurring integration is enabled. (Not all of them)

    Any idea?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,965 Super User 2025 Season 1 on at
    RE: "Invalid character value for cast specification"

    Hi D365FO user,

    Can you provide more details? Without additional information, we don't know what you did to encounter this error.

    You mention an entity export. Is this a standard or custon(ized) entity? If it is a custom entity, did you add coding or virtual columns to this entity? Is this happening on a production, UAT, or development environment?  Did it work before? If so, what exactly got changed? What steps did you do and on what exact moment do you get this error?

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,965 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,836 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans