Jeff: I seem to be having the same issue as RBC. I was actually reviewing this article to make sure that I am getting my URL correct for a button on the case summary screen that returns the user to a Property primary entity.
After creating a case (work order), I needed a way for the user to return to the property that the case was created for. Cases are only being created from the property entity so that the associated property id can be assigned to the case.
During the creation/testing of the button, I kept getting an error related to the tabs and I was able to determine that the error was due to the SQL restriction that RBC describes. I was trying to return the user to the cases tab on the property entity. There was a SQL restriction on that tab based on the stage of the property. I removed the restriction and thought I would be good. However, I still got the error. As I discovered, it does not matter which tab I returned the user to, the system will throw an error if ANY of the Property tabs have an SQL restriction. Therefore, I had to remove all the SQL restrictions in order to get the button on cases to work correctly.
However, I cannot leave it that way. I know there are at least 10 tabs that have restrictions as some only display during the Acquisition stage and some during the Ownership stage. Right now all tabs are displaying no matter what stage but I really need to get these back to how they were before the button on the cases was requested.
I don't see any other boxes on the tab screen that might allow a different way to restrict the display of the tab. Is there any other way to restrict the display of the tab (i.e. somewhere other than the tab screen?)
Also, in your reply to RBC, you recommend using a try/catch in the ASP page. I am assuming this will allow the system to ignore the error and proceed to the page. How might this try/catch look? Is there an example you can point me towards?
Any assistance would be greatly appreciated! Thank you!