Anytime I add a new Attribute, I get "Duplicate ID" error

BenHayat

Hi guys;

For the past few weeks, I get this annoying error "Duplicate ID. You must do 'CTRL-I' to resolve it", after adding a new attribute to an existing Object, and when I click on Test button.

So, I select the BSV, do a CTRL-I and I get confirmation, the Duplicate ID is removed and test continues. However, I notice that Aware also "Removed" another attribute from object and forms. The worst part is that I also loose all the Data for that column in Database.
Now it happens every time I add a new attribute.
I have exported and re-imported the BSV, but no help.

What's wrong? Has anyone run into this? If yes, what's the solution? I can't loose the data...
Thanks!

kklosson

There was a discussion a while back about loss of data wherein the configurator has not deleted any attribute but upon publishing the BSV discovered that a column had essentially been deleted then replaced resulting in loss of the column's data.

Please, if you can duplicated this, make a screencam video and get it to support.

BenHayat

kklosson wrote
There was a discussion a while back about loss of data wherein the configurator has not deleted any attribute but upon publishing the BSV discovered that a column had essentially been deleted then replaced resulting in loss of the column's data.

Please, if you can duplicated this, make a screencam video and get it to support.

I have sent info to support. I can't replicate it on a small new BSV. This problem began to manifest, once the BSV became larger. I don't know how a Screencam is going to show anything different than I described it. It's not like I'm fabricating this story. 😉
So, I hope support looks into this, because it has caused me grief, when I don't know what attribute was removed until it's too late.

kklosson

Exactly. But if you can demonstrate it on a screencam, and show that without removing a column or relation that it purges a data column, that's gold and gives support something to positively fix.

BenHayat

kklosson wrote
Exactly. But if you can demonstrate it on a screencam, and show that without removing a column or relation that it purges a data column, that's gold and gives support something to positively fix.

I'll try to catch it next time on video, but it's like a ghost. 😃

So, you're saying others have had this issue in the past, and do solution yet? 🙁

BenHayat

BenHayat wrote
So, you're saying others have had this issue in the past, and do solution yet? 🙁

I meant to say:

So, you're saying others have had this issue in the past, and no solution yet?

tford

Ben,

Does it happen each time you take the same steps with the larger BSV?

If so, why not send that BSV with the screencam to support?

kklosson

I had the issue but never related it to duplicate id. The recently added feature to view database changes when publishing was a result of the forum discussion.

BenHayat

tford wrote
Ben,

Does it happen each time you take the same steps with the larger BSV?

If so, why not send that BSV with the screencam to support?

I can't. The people behind the Project won't allow me sending the BSV.
It's either big BSV or large # of attributes or complex forms. It seems, it happens on large and complex objects.

It doesn't happen every time I add a new attribute. What it does happen, every time I get this "Duplicate ID" error, Aware, drops another attribute from database and all my forms and then, puts that back in in the object. Because of this, I loose the data that it dropped from the database, and I loose that attribute from all the forms. Today, I added for new attribute, saved and I clicked on Test, I got error. Press CTRIL-I, and test went through. When I went to customer form, "Last name" was missing from the form. Went back to Object Attributes, "Last Name" was there. Added it to Form, but guess what, I HAD LOST ALL THE LAST NAMES IN DATABASE. ALLLLLL! :cry:

kklosson

This is exactly the issue that was discussed in this post:
https://forum.awareim.com/d/6948>

Ever since this happened to me I have been very timid of publishing with any database changes. Support really needs a solid example of this happening, any way you can provide it.

BenHayat

kklosson wrote
This is exactly the issue that was discussed in this post:
https://forum.awareim.com/d/6948>

Ever since this happened to me I have been very timid of publishing with any database changes. Support really needs a solid example of this happening, any way you can provide it.

That post is from one year ago, which tells me this bug wasn't introduced lately. So, it has to do with growth or complexity of object/forms.

Now, I'm very nervous adding new attributes and I have to...
I really doubt a video makes any difference. if were the developer of Aware, I'd be looking at the routines that is coordinating between the configurator and the database Schema. Some ID is not getting incremented, (Duplicate ID) so you end up losing one attribute. A video is way too high level to pinpoint the problem internally.

I wonder why support has ignored it for over a year?

kklosson

I think the point is they just haven't experienced it and can't reproduce it. If I could walk through a video showing that all I did was add an attribute, then put it into test and see a data column purged, they would have to take this seriously (I think they do but have nothing to work with).

BenHayat

I doubt, this is an issue with MySQL. It's a problem in Aware, because it looses it in forms too. The error comes before it has even connected to Database. The error comes from Inspector. Perhaps it's the "CTRIL-I" routine that looses the column. But it's at Aware side and not Database.

customaware

Out of curiosity Ben....

Immediately AFTER doing a CTRL-I and being advised that it is fixed, do you select a Update and Keep Locked from the BS Context Menu?

BenHayat

eagles9999 wrote
Out of curiosity Ben....

Immediately AFTER doing a CTRL-I and being advised that it is fixed, do you select a Update and Keep Locked from the BS Context Menu?

Well, I click on the "Test" button, which in turn does the Update and lock.
I have not been able to detect If I I do something different to trigger it. Several months ago Kingsley warned me "don't throw too many things at Aware when changing database at one time". So, I'm very cautious to take baby steps at adding new attributes, but out of no where the error pops up.

BenHayat

Getting closer to go to production, I'm really nervous, because this problem looses data and your old backup, isn't going to match the new schema and new version of your program.

I hope support would look into this and tell us how to avoid it or fix it.

customaware

I used to get quite a few CTRL Eyes when I first started and was advised by support to make sure I clicked the Update and Keep Locked from the BS Context Menu immediately after...so I have done that ever since.

I rarely get them now and if I do then it is not really surprising as I have usually done something a bit funky in terms of changing attributes.

In my mind I try and be careful never to create an Attribute and delete it and then create one the same name in the same BO without putting into test in between times.

Also need to be careful doing that between publishing also I think

BenHayat

eagles9999 wrote
I used to get quite a few CTRL Eyes when I first started and was advised by support to make sure I clicked the Update and Keep Locked from the BS Context Menu immediately after...so I have done that ever since.

I rarely get them now and if I do then it is not really surprising as I have usually done something a bit funky in terms of changing attributes.

In my mind I try and be careful never to create an Attribute and delete it and then create one the same name in the same BO without putting into test in between times.

Also need to be careful doing that between publishing also I think

So Mark, you're saying to do the Update & Lock After doing CTRL-I or do Update & Lock after adding an Attribute?

If the former, then why does Duplicated ID error happens in the first place?
If latter, then I can do that to eliminate Duplicate ID error.

Please clarify what Support asked you to do do (or not to do) 🙂

customaware

Just to do Update and Keep Locked from the BS Context Menu after the Ctrl-I fix.

As to why?.... Some things are intended to remain a mystery for mortals such as myself. 😉

kklosson

Since the last flare-up on this topic, Support kindly added the feature to review database changes during publishing. If you put the bsv into test and observe this type of data loss, I would love it if you then published the BSV and checked the database changes to see if it captured this. Note that you don't have to actually publish, just go far enough to observe the changes. This is a data point we need.