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, ...
Answered

Virtual entity error when inserting record 'Number VER-000000 does not match format VER-######.'

(0) ShareShare
ReportReport
Posted on by 3,157
I have a power automate cloud flow that is attempting to insert into my dataverse table that was created from a custom data entity in F&O.
This field is the ServiceOrderId field.  I am attempting to send it a generic value so that it will create a new record using the number sequence specified in F&O.
 
This data entity works as expected when used with dual-write and custom dataverse tables.  I am able to send a value of '0000' and F&O creates a new ServiceOrderId for the record coming in.
 
In my dataentity I have overriden the 'initValue' with the following:

    public void initValue()
    {
        if (!this.skipNumberSequenceCheck())
        {
            NumberSeqRecordFieldHandler::enableNumberSequenceControlForField(
                this, fieldNum(VER_SMAServiceOrderHeaderEntity, ServiceOrderId), SMAParameters::numRefServiceOrderId());
        }
        super();
    }
 
As of yet I have been unable to debug anything coming into my data entity via the virtual entity table in dataverse.
I have the same question (0)
  • Hana Xue Profile Picture
    Microsoft Employee on at
    Hi,
    You can check out this document Configure number sequences and autonumber columns when using dual-write - Finance & Operations | Dynamics 365 | Microsoft Learn, which mentions that during the initial synchronization of dual-write, you may receive an error message similar to one of the following examples:
    Field ABC does not allow editing. Number CE-20000001 does not match format ######. Validations failed.
    Best Regards,
  • Verified answer
    b_radlyjames Profile Picture
    3,157 on at
    The solution to this problem is the following:
     
    Instead of using the primary key from the underlying table, in this case ServiceOrderId, create a new field and make it the primary key on the staging table and entity.  This will allow the ServiceOrderId value to be blank and the system to generate a value for you.

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... 512 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 386

#3
Adis Profile Picture

Adis 259 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans