Disappearing Child Objects

PointsWell

Suddenly one of my BOs has turned into a deadbeat BO and refuses to see any of its children.

I have checked the integrity of the Business Space and I have run the Cross Reference Rules and Check for Duplicate IDs.

I've interrogated the database with an independent SQL viewer and all the rows are on the Child BO table and visible.

I've also used AwareIM's search Objects from a blank VP and it seems that nothing from the child BO table is visible.

Is there something on the database that might have become corrupted / altered to make AIM forget about the child BOs?

kklosson

Have you looked at the raw data tables to ensure that reference attributes for this BO are being saved? I recommend you start there.

PointsWell

Hi, yeah I've checked the reference objects and they all present and correct which is why this one is a real head scratcher. It was all working until I updated a form layout and now AIM just refuses to see the records at all (even with an unfiltered query.

tford

It was all working until I updated a form layout

Have you tried to upload the prior BSV (the one prior to the form layout change)?

Hopefully you have a backup you can revert to.

BenHayat

PointsWell wrote
It was all working until I updated a form layout and now AIM just refuses to see the records at all (even with an unfiltered query.

A Very important question.
BEFORE you updated the form layout, did you add a NEW Attribute to BO and you did not run the UPDATE (to make changes to actual DB) BEFORE you changed the Form? Another words, you added a new attribute and went straight to Form and made changes and then started the test/update?
If yes, I bet there is at least one attribute lost from your BO. Check it against a previous copy and let me know. The lost attribute could be a reference to the parent BO.

PointsWell

I've checked both the SQL tables for my published version (which has not been updated with the changes yet) and my test version and the tables have all the same attributes on them. I had added an owned reference attribute to the top most level parent object but the BO is unrelated to the one that I am having the problem with.

I am going to run a test and delete all the data to see if this is a persistent issue or it is something that I can erase.

Though if I can 'fix' the problem by clearing all the test data I am still (more than) a little concerned by this

BenHayat

PointsWell wrote
I've checked both the SQL tables for my published version (which has not been updated with the changes yet) and my test version and the tables have all the same attributes on them. I had added an owned reference attribute to the top most level parent object but the BO is unrelated to the one that I am having the problem with.

I am going to run a test and delete all the data to see if this is a persistent issue or it is something that I can erase.

Though if I can 'fix' the problem by clearing all the test data I am still (more than) a little concerned by this

Aware's data system is rock solid. Anytime I had had problems, it was my fault. It's solid data system that has got me glued to Aware. I have to be fair and honest.

PointsWell

BenHayat wrote
Aware's data system is rock solid. Anytime I had had problems, it was my fault. It's solid data system that has got me glued to Aware. I have to be fair and honest.

Erasing my error on a forum is easier than in real life.

PointsWell

BenHayat wrote
Aware's data system is rock solid. Anytime I had had problems, it was my fault. It's solid data system that has got me glued to Aware. I have to be fair and honest.

For version 8.1 can a module be written to correct my typos, fix my mis-intentions and generally stop me typing when I am tired or under caffeinated.

Mistake identified as READ PROTECT not specifying the attribute to hide and instead hiding the whole Record.

I am sitting in the corner with a dunce hat on until I am suitably convinced that I have learned from my mistake.

customaware

Go to your room. No cake for you tonight. LMAO.