May be a query bug

vinsnash

The configuration tool let me use 'CurrentDate' rather than 'Current_Date' and save without reporting an error. Now there's an integrity problem "rule uses business object 'CurrentDate' which has not been found'.

It can't be corrected by going to the 'item rules' table of the query. When you click that button - now the error is reported and you can't get to it to correct.

Is there a way around this or does the query have to be deleted and recreated?

Thanks for the help

tford

Ironic that I just had this same scenario today. Mine did not involve CurrentDate, but I mistyped another BO name.

I just added a new query & deleted the old one.

vinsnash

Fortunately I had another query with the same result presentation but different criteria. I deleted the broken one, did a copy/paste, and rename and then change the selection criteria.

I would have hated to go through arranging the presentation columns again. That is tedious.

Vins

technopak

I came across this same problem and resolved it by simply giving the system what it was looking for - the missing object !

So just create a new object with the mis-typed name from the rule. It doesn't matter what configuration you give the new object, just a single attribute of type Plain Text will do fine. You will be deleting it again soon.

Once the object is created, your BSV integrity is fine once more and you can go back into your rule and correct the typo mistake.

Then simply delete the object you created to re-establish the BSV integrity.

And all is back to normal.

Regards,

Peter

tford

Great idea Peter! Thanks for sharing it.