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

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Work Order Auto-Number...
Microsoft Dynamics CRM (Archived)

Work Order Auto-Numbering is not working

(0) ShareShare
ReportReport
Posted on by Amer91 70

Hi,

Our Dynamics 365 Work Order Auto-Numbering is not working after one of the users has deleted the incremented number in the field.

Error status:

Script Error: One of the scripts for this record has caused an error. For more details, download the log file.

Any help is much appreciated.

*This post is locked for comments

I have the same question (0)
  • Amer91 Profile Picture
    Amer91 70 on at

    BTW on Sandbox we did the same thing, but the Auto-number is still generating with the same error message.

  • Thomas David Dayman Profile Picture
    Thomas David Dayman 11,323 on at

    Hi,

    Just so I understand. A user deleted the number within the field? Even though this field is usually read only?

  • Amer91 Profile Picture
    Amer91 70 on at

    Hi Thomas,

    Yes, a user deleted the auto-number from the field (It's not a read only field) and it's giving us this error since then, with null result.

    While the Auto-number still generating in Sandbox with the same error message!

    Thanks again

  • Thomas David Dayman Profile Picture
    Thomas David Dayman 11,323 on at

    In my instance the Work Order Number field is read only.

    What I would suggest is to query all your work orders in your CRM and find any Work Orders which have a null Work Order Number value and edit them so they have a valid number against them, make sure that there are no duplicates numbers.

    Maybe that could work?

  • Amer91 Profile Picture
    Amer91 70 on at

    I tried that, I gave all work orders a sequenced unique identifier based on PREF & number in the system, and then created a new WO, but it didn't work.

  • Thomas David Dayman Profile Picture
    Thomas David Dayman 11,323 on at

    Might have to contact Microsoft about this issue.

    What does the log file say?

  • antc Profile Picture
    antc 2,909 on at

    Can confirm all my instances WO name is RO.

  • Amer91 Profile Picture
    Amer91 70 on at

    System Job processes (Workflow) error: 

    A record required by this process could not be found.

    after entering or changing field's value(s) in Work Order page, an error message say: One of the scripts for this record has caused an error. For more details, download the log file.
    ReferenceError: OnChange (Function name) is not defined at eval (eval at RunHandlerInternal 

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

News and Announcements

Season of Giving Solutions is Here!

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#2
SA-08121319-0 Profile Picture

SA-08121319-0 2

#2
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans