XOG doesn't allow autonumbering for Resource
search cancel

XOG doesn't allow autonumbering for Resource

book

Article ID: 265224

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

After enabling autonumbering on the Resource object, then using XOG to create new Resources, the id isn't automatically populated, and the next_number doesn't increase.

STEPS TO REPRODUCE: 

1. Enable auto-numbering on the Resource Object Resource ID attribute.
2. Create a xog load for Resource, if you don't pass a value for the id, the load will fail (auto-numbering doesn't automatically occur via XOG).
3. Include the id in the load, and ensure it matches the "next_value" from this query: 
SELECT NEXT_VALUE FROM CMN_AUTONUM_SCHEMES WHERE OBJECT_CODE = 'resource' AND ATTRIBUTE_CODE = 'unique_name'

Expected Results: 

The next_value would increase, so that multiple Resources can be created in a single load transaction.

Actual Results:

The next_value never increases until a Resource is created in the UI

Environment

Release : 16.1.0

Resolution

This behavior is resolved in the upcoming 16.1.3. Autonumbering will function, just ensure that the id is empty in the XOG load. This was originally tracked as DE69732.