Unexpected behavior in a Lotus Notes programmable table

Question

I am developing a workflow database in Lotus Notes 6.0.3 (soon to upgrade to 8.5), and my OS is Windows XP.

I recently tried converting a tabbed table to a programmable one. It was so that I could control which tab was displayed to the user when it was open, so that they were presented as the most suitable for moving this document through the workflow. This piece of work works!

On one of the tabs there is a switch that controls the visibility of the next tab and a couple of cascading dialog boxes. One contains a static list of "Person":"Team" , and the other has a formula based on the first:

 view: =@If (PeerReview = "Team"; "GroupNames"; "GroupMembers"); @Unique(@DbColumn(""; ""; view; 1)) 

Dialogs have the property "Update fields when a keyword changes."

The behavior I did not expect is this. If the switch is set to Yes and a value is selected in one of the dialog boxes, the table opens the next tab. If the switch is set to "No" and the value is selected in one of the dialog boxes, the entire table is hidden.

I can duplicate the latter by disabling the "Refresh Fields When Changing Keyword" property in dialog boxes and instead pressing F9 after selecting a value. I have no idea why the first is happening. The table is called " RFCInfo ", and I have a field in the form of " $RFCInfo " that is edited, hidden from all users who did not select me and originally set by the Postopen script, which I can if necessary - this is, in fact, the Select Case statement , which looks at the specific value of an element and returns the name of the row of the table related to that value.

Can anyone suggest any pointers?

Answer 1

Hide - when the formulas in the table cells in the notes R5 and R6 were known for being unpredictable when you edited the table cells. Even in R7, I think they were still a little funky, but on R8 they were finally really solid. You did not show hide - when, but I assume that you are simply a victim of bad behavior.

Please do not shoot the messenger, but the usual way to solve this problem was to painstakingly recreate the entire table from scratch, and we hope that we will not have to edit it anymore. Ie, make a copy of the table in the form of a scratch and clean all the hidden objects - one by one. Then create a completely new empty table in the second scratch form and get all cells that are configured exactly the same as the original table, including nested tables, merged cells, and other parameters, but don't skip hiding for now. Then copy the contents of each cell from the first scratch shape to the corresponding cell of the second scratch shape. Then, referring to hide-whens in the original form, recreate each line - when the paragraphs in the cells of the second form are scratched. Finally, remove the original table from the original form, and then copy / paste the table from the second scratch back into the original form.

Answer 2

Once you have R8.5, go to XPages in Notes, you can easily implement your tabs. And in return you will get many other interesting questions to solve!