Attribute Required Not going away in Database

bucobill

I have an issue that maybe others have faced. I had a required attribute in a business object, however I have since turned it off as it would cause issues when doing duplicate and so forth. It is off in my current testing Business Space and works perfectly, which is the same file I use to import into the existing business space, however when I overwrite and import to the live business space that my users are assigned to I get the error that the attribute is required. I am using version 5.8. I don't know how to correct the issue can someone help?

Thank you

bucobill

I take it from the lack of response that no one has faced the issue before or maybe I didn't explain it properly. I had an attribute with required selected. I switched it to not being required however after importing the new version I still get the error that it is required but only when trying to duplicate item. Not when we do any other function. Help to fix this would be appreciated.

Rennur

I think you need to be more specific, very hard to help with such little information.
1) What is the Attribute type?
2) What is the actual error message?
3) What does the server log output show?
4) What does the Settings > Logging output say?
5) Are there any BO rules for this attribute?
6) Are there any redundant auto-generated rules?

When you import it to the live version, did you make that business space version operational, or it the old one still operational?

Cheers

Powerm

The error message will say " Form data invalid". This could be due to the BO.AttributeName you have deactivate as required or to an attribute of the same BO. It could be as well a required attribute you forgot to display on the Form.
The easiest way to solve the problem :

1- delete the BO.AttributeName you have set as required
2- publish the BSV
3- Create a new version
4- Recreate the BO.AttributeName with a different name, such as "BO.AttributeName1" or "BO.AttributeName2"
5- Publish and test

The problem might have occurred if that attribute is still marked as required on the database side...

Rennur

The easiest way is not always the best way.

Simply deleting the attribute you affects all relationships you have with that attribute including related rules of of other BOs, Shortcuts, queries, processes etc.
These integrity conflicts an will not let you put the version into test or publish it.

I would delete the attribute only if all else fails or there are not too many things related to it.

Powerm

You can export your bsv, rename it to what you want, import again and delete the BO....so no risk nor mess.

Rennur

I think it's better to investigate what is causing the issue to prevent if from happening again.

Powerm

I had it before, it was the MySql side still marking the attribute as required. It may happen during the creation/update of the tables by AwareIM, specially if you don't have enough assigned memory and have played too long with the bsv during the day.