M.App Enterprise Discussions

[s.rutka]

Hi!

I want to set up an analyzer view on a vectorset with reports and boundaries.

Using following setting:

• element data: meldungen_view
• boundary data: gemarkungen

(both out of same vectorset)

shows all reports but only one single boundary (out of 20). (Screenshot: fa1

After that I checked if primary key is set proper on that layer - it is.

If I change settings to:

• element data: gemarkungen

which means that I want to check if my boundaries are shown proper if I use them as element data, evry boundary is shown fine.

(Screenshot fa2)

Any ideas/tipps/hints? Or is that a bug?

Regards

Stefan

fa1.PNG ‏1130 KB

fa2.PNG ‏1121 KB

[DaveOke · Accepted solution]

Hi Stefan,

Feature Analyzer will determine if there is any feature data associated with a boundary record. If no feature data is associated, then the boundary geometry is removed from the display.

I've created a blacklog item to optonally allow displaying boundary features where no feature records are linked.

Thanks,

Dave

[gustavhf]

Hey!

I am having the same problem! Are there any ways to associate the feature data with the boundary data? I have a little over 400 polygon areas I would like to display, but only one is displayed. How can I fix this issue?

1.PNG ‏366 KB

2.PNG ‏456 KB

[s.rutka]

Can't you link them with a key field/external key field?

[gustavhf]

I set the key field to the same on both of them (both of the vector data has an equal column KOMMUNENUM). When I did this the result was the same with a slight difference. When the key is the same the polygon layer when set as boundary data dissapears when zooming in a little. There is set no scaling limit any way.

I am not entirily sure if I did it the correct way either. I set the key field under vector data as the same in both datas. Is there another way to link key/external key?

[gustavhf]

I made a little mistake with the key field, and updated the wrong vector data. Still the same error but this time without the zooming issue.

[gustavhf]

My mistake!! I didn't see the key/external key field under field setup. When i set that up it worked! Thanks for the help!