Updated to 4.9 and now have integrity errors that I cannot e

kklosson

As stated in subject line, I updated my instance to 4.9 and set off to regenerate my application but I got 27 integrity problems that by my estimation I should not have. All of them say:

rule " uses attribute [something] which has not been found

So the rule reference is apparently missing in the integrity check. I note that all of these errors point to Yes/No attribute. Hmmm. There are two rules that describe objects that are not found, but it is unclear which rule is in error. So to top this off, the normal function to edit the rule is not functional probably because the rule being referenced is ", or unknown.

My business space was in good order prior to updating. However, I have moved to a new machine. In doing so, I simply installed Aware IM, inserted a new License Key, and imported my last saved bsv file. I also restored a backup of my database to the new instance of the MySQL Server. This is just test data.

I have no idea what is wrong but it doesn't appear I will fix this on my own.

Need some help.

RocketRod

I have had this too but got it when I renamed a BO after it had rules attached. So I renamed it back and all was ok. I had the floating rules as well. Did you do something similar in your BS as that may help support track down the issue which there obviuosly is one.

Cheers Rod

kklosson

Yes I would expect this with renaming a business object but I simply exported this from a 4.8 instance then updated to 4.9 (and changed machines) then imported the previously saved BSV.

Odd that all integrity issues point to Yes/No attributes and most are reported twice in a row. There is one instance where the integrity check reports it cannot find an attribute but the attribute it says it can't find is actually the name of a business object.

I'm trying to see if there is some way to roll back 4.8 and see if it works there. That's kind of hard to do.

aware_support

It is very unlikely that the update to version 4.9 has introduced integrity errors. If you don't find the way to solve the problem send your BSV to us. We will charge you for investigation if this happens to be your problem and we will fix the problem with no charge for you if it happens to be a bug related to the update (which I doubt very much but you never know...)

kklosson

Thanks. You have it. Also, I keep iterations of my BSV going way back. I have a couple hundred. I went way back and all instances are producing the errors. I'm curious if you get any.

aware_support

Turns out that you had integrity problems in your icon rules before, but version 4.9 is stricter and it checks these rules for integrity, whereas the old version didn't. Build 1325 allows you to fix invalid icon rules.

PEFS

Is there a way to isolate where the problems are? I have a bsv with over 60 BOs and 130 forms and I have no guidance on where the icons are that are causing the problem.

kklosson

For me it was not too hard because I had only set icon rules on certain types of attributes. The error always at least told me the name of the attribute in question. I was able to find them that way. Other than that I know of no secret way to identify.