[SOLVED] Strange result for query field

Ok, I'm trying to work around the limitations set up.

So at the profile, I'm showing 'postnr' and 'by', and then I've moved the delimiter field to a 'not shown on profile'.
This makes it not show on profile view, so there I have to use two lines for the two fields showing there, this is clumsy but as per the limitations set up...
In the list I can then see the delimiter field, so far so good.

But when I go to edit the profile, it still shows the tab holding the delimiter field, despite that it's read-only, and it's on a 'not shown on profile'.

I do understand the argument, but you've locked the system to have security on the tab level, and not the field level, and tabs can not be shown combined, ie. 'two tab in one', and fields has to all be on the profile, and some fields can have contextual similarties, but have different security levels.

Field by field access is planned for CB 3.0 where we'll eliminate tabs all together in favor of "Field Container" fieldtypes.

But when I go to edit the profile, it still shows the tab holding the delimiter field, despite that it's read-only, and it's on a 'not shown on profile'.

You can use CB Privacy to remove the edit display of the delimiter tab.

Field container sounds interesting, as long as the containers can be manipulated and combined.
I just tried the privacy, and yes, that makes it work almost the way it's supposed to, but it's close and usable, thanks!