@Support;
The Database schema being different than BSV schema, wasn't the focus of this thread. The "Duplicate ID" was the subject and it is Aware that maintains and allocates IDs to attribute. I think we should stay focus on ID allocation algorithm, since that seems to be causing these problems. I know for fact I don't have schema issue, and during the attribute addition somehow the newly added attribute gets a number that already exists. This needs to be looked into.
Today, I did something different that support should take into consideration and that might help solving the Duplicate ID.
Here is how I used to do things and I would get error:
1) Add an attribute
2) click Save
3) Go to the object form and add the newly created attribute
4) Click Test
After the two dialog goes through I would get a Duplicate error. I would do CTRL-I and then click Test. After returning, I would notice another attribute was gone from the form. I'd put it back in the form, but it's data was gone.
How I did today, adding at least 10 attribute without a single error:
1) Update & Lock
2) Add attribute
3) Save object
4) Update & Lock
5) Test (To commit to DB)
6) Add attribute to form
No problem
The important difference here was that, I first Saved BSV, committed to BSV and then added to form.
Before I added attribute to form right after adding attribute to BSV and before saving BSV and committing to DB.
I think thats what throws Aware off, if you add the attribute to form right away, before saving and committing to BSV. That's my observation and so far it has worked for me.
