Custom Munlabels

[Jade.Freeman]

I thought I would post this here as we keep running into this same issue and have to keep trying to remember where we documented the solution

When customizing any of the default Munsys Label feature classes, or creating your own Munsys Label feature classes, it is important to ensure that the default query does not contain any complex logic. At MSU, we regurlarly use DECODE and CASE statements, as well as expressions which use columns from both the parent feature and the label feature tables, to format the label value, layer, color etc. This seems to give the MUNLOCK function a few problems resulting in a failure to lock the object.

We initially noticed the problem when trying to delete labels we had created. Munsys would give us a error indicating an invalid identifier error thus the object could not be locked and subsequentially not deleted.

To resolve, we have created a '___MUN - Munsys System Queries' query category (the triple underscore causes this group to sort to the bottom of the Query Palette). All users are given access to this query category and in this we place all default label queries. The actual queries any individual user sees are based on his permissions on the source table. We ensure that none of these queries use any complex logic as mentioned above. We then copy these queries to appropriate query categories and format as needed.

Additionally, Munsys Inc. gave us a script to run whenever we create a new label feature which fixes an issue with information getting stored in the wrong column.

UPDATE munsys_query SET txt_layer = '#' WHERE MUN_ID IN (SELECT mun_id FROM munsys_sp_tables WHERE mun_type = 1);

Hope this may help others who have seen this and at least we should be able to find this again!