Just to be clear, the tabs actually are working most of the time. I've implemented the tabs using rules and panels, as one would expect. Here, the default tab specifically will not display on the initial load when you go into "Edit Properties". It seems to be some sort of issue where it's looking for the last tab used, but can't find one and doesn't use the default that was set (I think). This can be solved by clicking on the other tab, which displays properly, and then clicking again on the original tab, after which there's no more problems.
My question is how can I make sure that it displays initially? Whether it be by custom JS or settings, I can't see a way to fix it.
There is one error in console that is thrown that I'm not sure if it's relevant, though since it looks to be in the nintex source might be something common that I don't know about (though I'm suspicious that it might be blocking the running of my JS).
Attached are images of what it looks like after the initial load, what it looks like after switching tabs, and the console error. I'm glad to provide other information as needed as well.
Thanks in advance.
So I managed to solve my specific problem, but there still is left the problem of the dissapearing defaults in edit properties mode. I have no clue if it's purposeful or not or if there's any way to disable/re-enable that. If anyone can provide some insight into that, that would be great, thanks.
I have the same problem! Could you please tell me how you were able to make the default tab display correctly on the initial loading of the form?
I had to change my approach rather than solve the problem. I was able to get by using some buttons to toggle the results instead of using the tabs
I tried a lot of ways and was able to get a "default tab" behavior to work by simply by not entering a default value in the choice control and using an "and is not blank" statement in the rule that hides the panel I want for default.
Edit: disregard the above, as this does not seem to be working after a save is performed ( I was just looking at the initial load and then view). Back to the drawing board or this might just be something I have to live with. It seems counter intuitive that this is not an OOTB variable function. Where the form button values are being stored?
Ok so this really bugged me and not being one to give in I looked at this all morning and found a solution that seems to be working.
Whether this is a good way to go, who knows. I'm weary of creating more pseudo-data columns but I will run with it for now. Anyone else tried this or see any issues with this?
I was looking for the solution for quite sometime now. I have tried your steps. It worked fine for me. Did you experienced any issue by connecting two controls to a single column lately?
Hi Noa, glad to hear it worked. This is the only scenario I have used multiple controls on a single column and I haven't noticed any issues. (other than having to add extra lines to my documentation ) If I run into any I will post it here.