Environment

• System: ENOVIA/3DEXPERIENCE On-Premise

• Topic: Auto Name Series

• Object Name: type_ProjectSpace

• Object Type: eService Object Generator

• Object Revision: ObjGen_test

• Policy: eService Object Generator

• Object: 'eService Object Generator' type_ProjectSpace ObjGen_test

Problem Statement

Hello everyone,

I have predefined Auto Name series that shows in a drop-down menu in the Project Management app. Each entry in the menu represents a BO (eService Object Generator) with defined attributes like Prefix and Suffix.

The name that actually appears in the drop-down menu is the REVISION of the BO. Now the client has requested a modification to this name (which in our terminology means modification to the revision).

According to this, I am no longer going to use the modify businessobject command because this is not an attribute that I am trying to modify. Thus, I want to take a revision. According to the BO Policy, only Major Revisions are set to TRUE.

What I've Tried

1. Modifying the Revision Directly

MQL> mod bus ID revision REVISIONNAME;

Result:

Error: #1900068: mod business object failed
Error: #1500096: The revision of a business object cannot be changed without revising the business object or changing the business object name.

2. Major Revision (with new name)

MQL> revise businessobject 'eService Object Generator' 'type_ProjectSpace' 'ObjGen_test' major to 'ObjGen_test2';

Result:

Error: #1900068: revise business object failed
Error: #1500821: Business Object ''eService Object Generator' type_ProjectSpace ObjGen_test_kady' is not major revisionable.

What I've Checked

1. Policy Configuration

The policy eService Object Generator shows:

state Exists
    minorrevisionable false
    majorrevisionable true ✅
    versionable false
    promote false
    checkout history true
    published false

Result: majorrevisionable is set to true.

2. Business Object State

Printing the BO shows:

current state Exists
    status enabled
    attained 4/28/2026 2:43:30 PM
    minorrevisionable no
    majorrevisionable yes ✅
    published no
    versionable no
    access all

Result: The object's current state also shows majorrevisionable yes.

3. Object Lock Status

The object is unlocked and locking not enforced.

4. Policy States

The policy eService Object Generator has only one state (Exists).

Questions

1. Why does the system say the object is "not major revisionable" when both the policy and the object state show majorrevisionable true?

2. Does the policy need a revision sequence (e.g., majorsequence) to be defined for revisions to work?

3. What is the best practice to fulfill this request?

Any insights or suggestions would be greatly appreciated!

Thank you in advance for your help.