Is there a way to bulk configure the location property of points to "Static" (About a thousand points). I tried using the Bulk Editor, but it can only be a boolean. I tried setting it to True, but it didn't help either. Maybe there is an Aggregate I should look into and write a script? What would be the recommended way?
Solved! Go to Solution.
To the best of my knowledge the location of a point is "Inherited" from the Parent Group, and if that parent Group has its location "Inherited" it could come from as far up the DB Tree as the Root. So I would think the easy way is to make sure that all of the points and groups have the location set to inherited down to a specific group containing your ~1000 points, then change that group to "Static" and enter the new location information. Then all of the points within that group should be good.
Looks like it is a bug in the Bulk Edit tool. You should report it to your local Schneider support team.
Since the Bulk Edit does not work I would change it using SQL the value to update that property to, will be a 1.
There are 4 options to set for the source and their numeric values are 0-3, Static is the second one so it is 1.
Nor should it 🙂
If the child items are set to 'Inherited' for the GeoLocationSource property then they will have the GeoLocationLatitude and GeoLocationLongitude of their parent group.
Depending on how you intend on using the Geo Location configuration will determine if this works for you or doesn't.
My recommendation is to have the GeoLocationSource defined as 'Static' or 'Dynamic' as high up the tree as makes sense for your application. I would normally NOT consider this to be at a point level. Since points would normally be associated with a group which represents a device, or a group of such devices which represent a site.
I don't see significant benefit in having GeoLocation tagged for 'Fault', when it could instead be tagged for 'Pump 1', or for 'SPS234 - Martin Ave'.
When you do a query, the GeoLocationSource = 'True' appears to be for anything except for 'Inherited' / 'None'.
Which is normally ideal, as long as you have it only set to 'Static' / 'Dynamic' at sensible locations.
Having a dozen stacked map symbols for Running, Fault, Manual, Auto, Current, No Flow, Duty all because you have set each of these pump point as 'Static' is bad... mmmkkaaayy...
Having a single item which represents the Pump location 'may' be better... (I would perhaps do this in a lagoon system, or a large treatment plant).. for sites like SPSs where the pumps and well are naturally so close together, then I would ONLY have 'Static' set at the site group, and all items beneath it will 'Inherit' this location.
Can you include your full SQL query?
I agree. I think I should have explained it better. I need to set the Location for 1000 different sites (not points, I was just using points as a proof of concept for now). I need to change the GeoLocationSource Property to Static for all of them. Would you please be able to recommend a way to do that?
On the SQL front, I don't believe you had.
I think this may indeed be a bug, although it's been a while since I played around with SQL and aggregates also, so perhaps I'm also doing it wrong.
It would be worth you reporting it to Tech Support. There's potentially two situations:
a) We're all doing the query wrong, in which case great. It's just the documentation situation that needs to be improved.
b) There is a valid bug. In which case the bug should be fixed, and the documentation situation should be improved.
Update CDBObject SET GISLocationSource = 1 WHERE Id =(SELECT Id FROM CDBObject WHERE FullName LIKE 'Example Projects.Internal.Bla.Bla point)
*** Prepare failed - Query error. ***
*** Column GISLOCATIONSOURCE expects type Boolean, but 1 is Integer.
Cannot write to column 'GISLocationSource'. ***
The answer is:
c) There is no interface to create aggregates or switch between them from SQL. You may request this feature through support.
@sbeadle Is it expected that the Bulk Edit Tool should have been capable of this kind of functionality?
Maybe it's a double request situation.
Hi @BevanWeiss . Yes, I think so. At the time it was created I am not sure that aggregates with multiple child choices existed or were commonly needed to be edited, so the Bulk Editor did not need to support it. This should be asked of the support team.