I am getting this error message when I try to edit a proportional symbol map I created in InfoAssist:

Code: 1095 Type: xFDMinit
the metadata for ENTERPRISE_ANALYTICS/MST_CRM_ACCOUNT is accessed, but not loaded(IA_190716_121057-1)(IA_190716_121057-1)

The issue seems to be when I use a field that isn't defined as a GEOMETRY_POINT (maybe a STATE or COUNTY or LATITUDE). It runs fine when I first create it, but if I try to go back in to edit the map I get the error. When I use a GEOMETRY_POINT field, I don't get the error. Has anyone else encountered this?

This message has been edited. Last edited by: FP Mod Chuck,

When you create this map do you use the Size bucket or only color? Are there missing values in either size or color?

Actually tried with size bucket only, color bucket only and neither. Tried excluding MISSING values in both Lat and Long fields. None of that fixed the error.

We found that if we define a geometry point field in the master file (using the lat/long fields and the "WKID" - whatever that is) then use that instead of lat/long in the map, we don't get the error. Seems like there is a bug -- why can't I just use lat/long in the IA map?

Another WF quirk, I guess.

Given a WKID (Well-Known ID) spatial reference, longitude, and latitude, the GIS_POINT function builds a JSON point defining a Geometry object with the provided WKID, longitude, and latitude. The function is optimized for those SQL engines that can build a JSON geometry object. This is actually an ArcGIS concept described here: https://developers.arcgis.com/.../spatial-references/

Here's the example from the manual. Does this work for you? I don't think it's a quirk. The function creates the geopoint the same way as it does in the master. I think having it in the master makes more sense, since users shouldn't have to figure out how to deal with lat/long in IA.

  
DEFINE FILE WF_RETAIL_LITE
GPOINT/A200 = GIS_POINT('4326', STATE_PROV_CAPITAL_LONGITUDE, STATE_PROV_CAPITAL_LATITUDE);
END
TABLE FILE WF_RETAIL_LITE
SUM FST.STATE_PROV_CAPITAL_LONGITUDE AS Longitude
FST.STATE_PROV_CAPITAL_LATITUDE AS Latitude 
FST.GPOINT AS Point
BY STATE_PROV_CAPITAL_NAME AS Capital
WHERE COUNTRY_NAME EQ 'United States'
WHERE STATE_PROV_CAPITAL_NAME LT 'C'
ON TABLE SET PAGE NOPAGE
END

This message has been edited. Last edited by: BabakNYC,

If I add Latitude or Longitude in the location layer in IA, it pops up a window to set the field's geographic role and the associated coordinate field. When I click okay, it replaces the field I put under Layer with a defined "Lattitude_Longitude_Point" field which is defined using the Geo_point function. I guess I'm seeing it as a quirk because why does that then cause an unrecoverable error after I save the map? I can still run it, I just can edit it.
I think I will create the geo_point in all the applicable master files anyway.

Additional information -- it appears to only be a problem if a JOIN is involved. When only one master file is being used, it doesn't error on edit.

This message has been edited. Last edited by: DWaybright,