Can you post the XML of what you have so we can take a look at it? If you can in detail explain what you’re doing and why you’re doing it that way, we might be able to help.

---

So, I have two tabs with two tables. Both the tables run on the same model but shows different set of records based on a condition. I am trying to activate that condition on click of the tab otherwise I have to create two models to show different data in the two tables. 

---

Shalabh - are you sure that you are both setting the conditions and requerying the models?   Just setting the conditions will not actually update the data. 

---

Yep, I am activating the condition first and then querying the model.

---

Shalabh,

What version of Skuid are you using?  I just tried this in 11.1.1.  It definitely works.

One other way you can do this is to remove the 2nd table component and then pull the remaining table below the tab component.  This will make the single table component visible no matter what tab you select.  You would then be using the tab component as a simple control to set the conditions on a single table.

Thanks,

Bill

---

Hello, I believe I’m having the same issue. I have an action set to fire on the Model “ActivitiesOpen” when the condition labeled “Subject” is activated. It’s supposed to activate a condition on he “ActivitiesCompleted” model and then re-query the model. However, its not working.

I even checked Chrome Console with skuid.model.getModel(‘ActivitesCompleted’) and it shows the model as inactive, but the condition on the ActivitiesOpen goes from inactive to active.

I’m on 11.2.6 on Salesforce. Here’s my XML for those models.

condition.activated


Subject

---

Actually, I just found how to fix it, but I still think it’s a bug. 

I have a filter on a Filter Set with the following options
Filter Type: Select Option
Filter Method: Server
Pick Options and Conditions(s): Manually
Model Condition to Affect: Subject

The Source Type of the filter is Manual and I have 2 options. 

In order to fix the problem, I changed the properties on the manual options I created from “What Conditions will this Option affect?” from “Affect Default Condition” to “Affect Other Condition(s)” and then added an Action to Activate the Condition.

It’s doing the same thing as if I had selected “Affect Default Condition” but for some reason that doesn’t fire the Action event on the model.

---