topic Re: How to avoid reducing outer dimensions in QlikView

How to avoid reducing outer dimensions

Mon, 26 Jan 2026 18:19:17 GMT

Assuming we had the following QlikView tables i the document:

Orders

Order Number

State

States

State

Country

with contents:

Orders

1 NY

2 NY

3 FL

4 OH

State

NY USA

FL USA

OH USA

I'll do Section Access and reduce on Order Number. Suppose a specific user is only authorized to Order 3 & 4. In addition to the data in Orders being reduces to 3 & 4, the data in State will be reduced to only FL and OH.

How do I do the reduction, but specify that I don't want the data in table State to be reduced? I would still want other connected tables to be reduced.

Any ideas?

Thanks!

Re: How to avoid reducing outer dimensions

swuehl — Wed, 03 Feb 2016 19:43:32 GMT

You can add records to your order table like

Dummy, NY

Dummy, FL

Dummy, OH

i.e. a dummy order per state.

then add for each user authorization for Dummy order.

Re: How to avoid reducing outer dimensions

Wed, 03 Feb 2016 19:52:59 GMT

Unfortunately, I can't add any order data that doesn't really exist. It will cause issues elsewhere..

Re: How to avoid reducing outer dimensions

swuehl — Wed, 03 Feb 2016 21:17:33 GMT

You don't need to add any real fact measures.

But I am just offering a general idea / approach, you probably need to adapt it to your setting and requirements.

Re: How to avoid reducing outer dimensions

lblumenfeld — Wed, 03 Feb 2016 21:24:50 GMT

can I simply add another column to the section access table and add those values? First r example

User, Order, State

joe, 1, null

joe, 2, null

joe, null, NY

joe, null, FL

joe, null, OH

would that work?

‌

Re: How to avoid reducing outer dimensions

swuehl — Wed, 03 Feb 2016 21:33:53 GMT

What is 'null' in this sample? An existing field value?

You can try yourself by creating a small sample app, but I don't think this will work.

Re: How to avoid reducing outer dimensions

lblumenfeld — Wed, 03 Feb 2016 21:50:48 GMT

No. It's just "nothing supplied" for that value.

Re: How to avoid reducing outer dimensions

Thu, 04 Feb 2016 04:48:57 GMT

can I simply add another column to the section access table and add those values? First r example

User, Order, State

joe, 1, null

joe, 2, null

joe, null, NY

joe, null, FL

joe, null, OH

(The nulls would be no value on that line.)

would that work?

Re: How to avoid reducing outer dimensions

rwunderlich — Fri, 05 Feb 2016 02:29:18 GMT

‌I think what you are suggesting is exactly what Stefan was suggesting. But you can't add the data in the section access, it has to be in the section application. if you want to keep state values that have existing orders, you will have to create dummy values for whatever your reduction field is to keep them in.

Rob

Re: How to avoid reducing outer dimensions

Fri, 05 Feb 2016 03:07:04 GMT

‌Rob,

im assuming that I wouldnt have to create dummy orders (I can't do that.) I have a table that explicitly has states and one that has orders. So the way I set up the reduction table (above) wouldn't it reduce the orders for Joe, but still let him see the explicitly authorized states even if the are no orders for those?

thanks,

LEslie

Re: How to avoid reducing outer dimensions

swuehl — Fri, 05 Feb 2016 13:08:26 GMT

Leslie,

section access with data reduction is adding a 'reduce to possible values' after applying selections based on the reduction field values for the logged in user.

So, to develop a solution to your requirement, forget about the section access table for now.

You need to develop a data model, that fulfills your requirement (limiting the possible record set to only values the user is allowed to see, but without removing dimensional values he needs to see) just by making selections in fields of your data model.

If you've created such a data model, creating the section access table should be easy then.

Hence you need to create a data model where you can limit - for any given user scenario - the order number by making selections. This selection shall not limit the possible state values.

I believe my suggested data model fulfills your requirement. You may have some additional requirements or you are using the order number field in some expressions where additional DUMMY values are unwanted (well, it looks like a key field, so you probably shouldn't do this anyway).

You can think about creating an additional field in your order table to handle this:

Orders:

REDUCTION, Order Number, State

1, 1, NY

2, 2 , NY

3, 3, FL

4, 4 , OH

DUMMY, , NY

DUMMY, ,FL

DUMMY, OH

If your user should only see order number 3 and 4, create a section access table that authorizes him to REDUCTION field values, 3,4, DUMMY.

Now he sees only Order number 3 and 4, but still all states values.

[

You can automate the creation of the additional DUMMY values by concatenating your distinct State values together with a constant DUMMY value to Orders table:

CONCATENATE (Orders)

LOAD 'DUMMY' as REDUCTION, State

RESIDENT StateDimensionalTable;

]

Hope this helps,

Stefan

Re: How to avoid reducing outer dimensions

lblumenfeld — Thu, 02 Jun 2016 13:45:12 GMT

Rob,

I did end up going with a slightly modified version of the dummy records and it works really well.

Thanks,

Leslie

Re: How to avoid reducing outer dimensions

lblumenfeld — Thu, 02 Jun 2016 13:47:59 GMT

How do I mark this post as answered?

Re: How to avoid reducing outer dimensions

oknotsen — Thu, 02 Jun 2016 13:57:08 GMT

Click on the "Correct Answer" image on the post that is the correct answer.

Re: How to avoid reducing outer dimensions

lblumenfeld — Thu, 02 Jun 2016 14:04:15 GMT

There is none. All I have are "actions," "like," and "reply."

Re: How to avoid reducing outer dimensions

Anonymous — Thu, 02 Jun 2016 16:23:29 GMT

Hi Leslie,

Please see this post for details on Marking Replies as Correct or Helpful. Let me know if you need any further assistance.

Best regards,

Qlik Community Team

Re: How to avoid reducing outer dimensions

swuehl — Thu, 02 Jun 2016 16:31:13 GMT

Leslie,

are you using a different account now vs. the time you've created the thread?

Seems like there are two different accounts in this thread.

You can only close the thread using the same account that was used for creating the thread.

Regards,

Stefan

Re: How to avoid reducing outer dimensions

Peter_Cammaert — Thu, 02 Jun 2016 17:09:48 GMT

You created this discussion with an account called meridian_lblumenfeld. You're now posting using an account called lblumenfeld. Those are different accounts. Do you still have access to the other account?

Re: How to avoid reducing outer dimensions

Peter_Cammaert — Thu, 02 Jun 2016 19:30:37 GMT

If not, you can always try asking one of the Community Moderators/Managers like Jeremy, Onno or Sara to close it for you.

Best,

Peter