Calculated Dimension on Qlik Sense Map Objects?

[#1]

It seems that when I create a calculated dimension, it does not come up as an option when I want to add it as a point layer to a map object in sense. Only uncalculated fields or dimensions show up as available options. Is that the case or am I missing something?

Thanks

[#2]

Hi,

You can use Calculated Dimensions as Point Layer in a Map. It works totally fine.

Here Year is a simple calculated field.

And it appears in your Point Layer Option.

Regards,

Rohan

[#3]

Hi notbuyingit,

first du you have GeoMap.Latitude, GeoMap.Longitude for the place u want to add a value to?

Here is a vid that helped me creating my first pointmap in Qlik Sense

Using the Maps Chart Object - Points Maps - Part 1 - (video)

[alextimofeyev]

It seems to be the case. Can you move calculation to the data load script, so that your dimension can be simply derived from a field?

[#5]

Hi Alex,

i did the calculation in the formular field so u dont need to do all in script.

but i agreee its a lot easier in the app to manage.

[alextimofeyev]

Eric,

I meant to respond to notbuyingit's original post, not your comment. Sorry about the confusion.

Alex !

[#7]

np, it was just an add of opinion to push ur comment.

[#8]

Hi Eric,

Thanks for the reply! I'm very familiar with this video and already have my maps up and running with the appropriate geo-coordinates included. My main question has to do with what happens when you create a calculated dimension not in the load script, but within the app, saved as dimension, and wish to use that calculated dimension as the point layer. The map object doesn't seem to recognize any dimensions that are calculated in the app, only those that are pre-calculated in the load script. Does this clarify?

Thanks again!

[#9]

Thanks Alex! Glad you confirmed my issue. I had thought about creating in the load script as a backup, but one of the reasons that was not my first choice is because the logic I'm using in the calculated dimension, relies on 5 or more table joins that is already done in the app, whereas I would need to create that long query statement within the load script.

It's possible to do, but with the potential that we may want to create several calculated dimensions on the fly, and the fact that you can create and save calculated dimensions within the app to be used in charts and table objects, etc., I thought it would be great to leverage those dimensions in the map object as well.

Thanks again and let me know if you can think of any thing else that could help.

[#10]

Thanks for the reply Rohan. I'm looking for a way to use calculated dimensions without generating them in the load script first.