InfoPath Dev

 

I have a repeating table(B) inside another repeating table(A). Currently i have face the difficulty to disable the repeating table B that "Don't allow user to insert or delete this control" but can disable A repeating A.

 

myFields

  group1(repeating table A)

    field1

    field2

    group2 (repeating table B)

      field3

      field4

      field5

 

From the situation above, i have a dropdownlist in the form that contain value New, In Progress and Completed named it as Status. I create a formatting rule for repeating table A and repeating table B that disable the "Don't allow user to insert or delete this control" with condition "Status is not blank". When i preview the form, repeating table A is not allow to insert item but repeating table B is allow. Is it any wrong on the formatting rule or my design of the two repeating table? Can everyone know the solution or know how to write code behind to control the repeating table that not allow to insert or delete item?

check if attachment helps

 What you mean check if attachment helps? In my case, i just wanna disable the repeating table A and B not allow to insert and delete item when the status = "Completed".

 I had download the attachment and test on it. The 1st Repeating Table is disable when the status = new, the field8 display as new but the 2nd repeating table still able insert new item.

hi vick yong,

i am not sure about your schema,  the attached template contains two senarios, check which one matches your scenario and use that.

 

 Hi, Can you check for me the infopath form i attached? Why when i select the status to "Completed" then 2nd repeating table still able to insert/delete item?

Is it i configure wrongly or any solution to solve this problem? Thanks. I am using infopath designer 2010 to create the form.

Yes I am having the same exact problem illustrated here, in browser form style.

You can get around this issue by adding some code to the "changing" event on the outer and inner repeating tables and cancel the event, but if you are using a browser-enabled form, you cannot access the changing event.

I have spent almost a full day on this issue and there seems to be no workaround.

I think microsoft labeled this as a known bug in 2006, see the following KB: http://support.microsoft.com/kb/928042

This was in 2006, is this still a bug in infopath 2010?

Can anyone suggest a workaround?

I am trying to deliver on a promise to my clients of something assumed to be easily done.

To anyone running into this *easily recreated* bug in infopath, the workaround I am using is to create custom insert/delete buttons that duplicate the built-in functionality but ensure against unwanted table manipulations in the form code itself. If anyone has a better suggestion, please post it in here.