If all three there, ATG should generated order with order defined in idspace.
Deleting das_id_generator entries for idspace can cause ids being used twice, Be careful if deleting idspace from table.
If you have the out of the box configuration it will be as easy as just run this update:
select * from sfc_content_promotional;update DAS_ID_GENERATOR set prefix = 'A' where id_space_name = 'order'; and restart the server.
I agree with NitinDubey, do not delete anything on das_id_generator.
Thanks all for your help. I have updated the table with these values and its working. But going forward if I set up my qa or production env, will I have to do this again and again.? Cant it be made like the das_id_generator takes its values by default?
I have OOB configuration only. I have created only idspace xml file. I can see it via dyn/admin but order ids doesnt get generated in the way I want unless i go n update the table once.
Also is there any way to configure the upper limit also say I want order ids between 1-100. I will define seed as 1 but any way to configure100 also?
In response to upper limit
No OOTB it can't be done.U need cutomize.
We had similar requirements to restrict order ids for some fixed length, We are not using id generator.
For customization,There are many options:
1. Customize SQL Id generator.
2. Pass ur order id as parameter while creating order. createOrder(java.lang.String pProfileId, java.lang.String pOrderId, java.lang.String pOrderType)
3.Create new property and rely on that, This way atg will rely on order repository id and ur module can rely on ur property.WE are following this.
As far as I know: OOTB implementation doesn't support that.
U need to created ur own idgenerator say MySQLIdGenerator ,U can also extend SQLIdgeneraor to easier implementation.
Caution: specify MySQLIdGenerator in order repository only.
This way ur generator will be called only for order ids, and other ids will be generated by ATG implementation of SQLIdgenerator..