Latest Contributions by EricGardecki1

I am seeing this error in the browser console after clicking the edit icon for related records: TypeError: Cannot read property 'toLowerCase' of undefined ... View more

I had added it at one time but removed it the last try in case that was the issue.   This time around I added FID again but still having the same problem. Any other thoughts? ... View more

https://services9.arcgis.com/6qDS6gU30E3aEaoi/ArcGIS/rest/services/StormSewer_Points/FeatureServer  ... View more

I removed the layer and readded.  I'm still having my same issue. When I try to add a related record in a web app, the window just seems to hang and I can't hit the "+". In Collector, when I try to add a new record to related table, it simply says "Update Failed"  "Updates could not be sent". Any suggestions? ... View more

via deleteFromDefinition? Last time I tried I ended up with 2 relationships so I thought there was a better way but I can try again. Do you see anything wrong with my JSON for adding the related table with editing tracking?  I don't know why the relationship isn't working and that is the only thing I have changed this time around.  I really wanted it to auto-create the date of edit so I didn't need the users to have to enter the date manually. ... View more

khaled hassan‌ you mentioned "dropping" a relationship above.  Can you tell me how this is done?  I can't seem to figure it out. I ran into some sort of issue with the related table so i want to reverse everything.  I need to remove the relationship and then remove the related table and start over.  I do not want to have to delete the service entirely and start over completely.  I tried using the updateDefinition and deleteFromDefinition and everything I do just seems to stay there anyway after submitting. What I tried to do was when adding the related table, include the fields for edit/create/editor/creator.  But doing so seems to have messed things up so I want to revert back to a more simple related table.  Unless you can tell me what I may have messed up with adding those fields?  Here is what I used: { "layers" : [ { "name" : "Maintenance", "type" : "Table", "editFieldsInfo" : { "creationDateField" : "CreationDate", "creatorField" : "Creator", "editDateField" : "EditDate", "editorField" : "Editor" }, "editingInfo" : { "lastEditDate" : " " }, "fields" : [ { "name" : "reference", "type" : "esriFieldTypeGUID", "alias" : "reference", "sqlType" : "sqlTypeOther", "nullable" : false, "editable" : true, "length" : 38, "visible" : true, "domain" : null, "defaultValue" : null }, { "name" : "MaintDate", "type" : "esriFieldTypeDate", "alias" : "Maintenance Date", "sqlType" : "sqlTypeOther", "length" : 8, "nullable" : true, "editable" : true, "domain" : null, "defaultValue" : null }, { "name" : "MaintType", "type" : "esriFieldTypeString", "actualType" : "nvarchar", "alias" : "Maintenance Type", "sqlType" : "sqlTypeNVarchar", "length" : 256, "nullable" : true, "editable" : true, "visible" : true, "domain" : null, "defaultValue" : null }, { "name" : "Notes", "type" : "esriFieldTypeString", "actualType" : "nvarchar", "alias" : "Notes", "sqlType" : "sqlTypeNVarchar", "length" : 256, "nullable" : true, "editable" : true, "visible" : true, "domain" : null, "defaultValue" : null }, { "name" : "CreationDate", "type" : "esriFieldTypeDate", "alias" : "CreationDate", "sqlType" : "sqlTypeOther", "length" : 8, "nullable" : true, "editable" : false, "domain" : null, "defaultValue" : null }, { "name" : "Creator", "type" : "esriFieldTypeString", "alias" : "Creator", "sqlType" : "sqlTypeOther", "length" : 50, "nullable" : true, "editable" : false, "domain" : null, "defaultValue" : null }, { "name" : "EditDate", "type" : "esriFieldTypeDate", "alias" : "EditDate", "sqlType" : "sqlTypeOther", "length" : 8, "nullable" : true, "editable" : false, "domain" : null, "defaultValue" : null }, { "name" : "Editor", "type" : "esriFieldTypeString", "alias" : "Editor", "sqlType" : "sqlTypeOther", "length" : 50, "nullable" : true, "editable" : false, "domain" : null, "defaultValue" : null }, { "name" : "FID", "type" : "esriFieldTypeInteger", "actualType" : "int", "alias" : "FID", "sqlType" : "sqlTypeInteger", "length" : 4, "nullable" : false, "editable" : false, "domain" : null, "defaultValue" : null } ] } ] } Can you assist? Thanks! ... View more

That worked.  I recreated everything and can add the related records.  I am unable to see the related records through the default popup and such but I can through the data table and via custom arcade based popup. Still can't export as FGDB but I really don't have a reason too so I suppose it doesn't matter.   Thanks for all your help. ... View more

It is shared with everyone, but let's try this new one...also shared with everyone.  https://karta.maps.arcgis.com/home/item.html?id=464779f8f45b4d1bb122436d61c84947  https://services8.arcgis.com/1M05Hr7CGeTQZWv2/arcgis/rest/services/Catch_Basins/FeatureServer  thanks ... View more

Khaled, I started out with a new feature layer created through AGOL.  Added the 2nd layer and relationship as below.  When I attempt to add a record to the related table, it seems to go through (no errors) but it is not shown anywhere.  The table remains empty. Also, when I tried to export this feature layer as a FGDB, it also seems to fail in some way.  The export screen stays up as if it is frozen.  A file is created but it seems corrupt as I can't open it. I'm guessing I must be doing something wrong with the JSON.  Suggestions? For adding layer: { "layers" : [ { "name" : "Inspections", "type" : "Table", "fields" : [ { "name" : "reference",  "type" : "esriFieldTypeGUID",  "alias" : "reference",  "sqlType" : "sqlTypeOther",  "nullable" : false,  "editable" : false, "length" : 38,  "visible" : true,  "domain" : null,  "defaultValue" : null },  { "name" : "Insp_date",  "type" : "esriFieldTypeDate",  "actualType" : "datetime2",  "alias" : "Insp_date",  "sqlType" : "sqlTypeTimestamp2",  "length" : 8,  "nullable" : true,  "editable" : true,  "visible" : true,  "domain" : null,  "defaultValue" : null },  { "name" : "notes",  "type" : "esriFieldTypeString",  "actualType" : "nvarchar",  "alias" : "notes",  "sqlType" : "sqlTypeNVarchar",  "length" : 256,  "nullable" : true,  "editable" : true,  "visible" : true,  "domain" : null,  "defaultValue" : null },  { "name" : "ObjectId",  "type" : "esriFieldTypeOID",  "actualType" : "int",  "alias" : "ObjectId",  "sqlType" : "sqlTypeInteger",  "nullable" : false,  "editable" : false,  "visible" : true,  "domain" : null,  "defaultValue" : null } ] } ] }  for adding relationship: { "layers" : [ { "id" : 0, "relationships" : [ { "id" : 1, "name" : "Inspections", "relatedTableId" : 1, "cardinality" : "esriRelCardinalityOneToMany", "role" : "esriRelRoleOrigin", "keyField" : "GlobalID", "composite" : false } ] }, { "id" : 1, "relationships" : [ { "id" : 1, "name" : "Inspections", "relatedTableId" : 0, "cardinality" : "esriRelCardinalityOneToMany", "role" : "esriRelRoleDestination", "keyField" : "reference", "composite" : false } ] } ] }   Suggestions? ... View more

https://karta.maps.arcgis.com/home/item.html?id=df19163199f84d7b89a9f4069ac1e288#overview   This is just fake data I'm testing with. I did some further testing and it appears that the export only doesn't work on some of the layers.  Perhaps I'll just start over with some fresh data. ... View more

Xander Bakker‌ I'd like to symbolize a layer based upon data in the related table.  Particularly, with a layer of catch basins, and a related table of inspections that contain a date.  I'd like to display the catch basins in a manner such as those inspected this year be green and the others, red.  Is this doable? You also mentioned visualizing the related data better in the popup...can the popup list all of the related data without having to open it separately? Thanks! ... View more

Every time I try to export to FGDB it seems to create one that is corrupt.  I can't use it in AGOL and once downloaded, the zip can't be opened.  I have tried with multiple feature services.  Can you verify that there is no bug?  Suggestions? ... View more

I am just testing at this time with sample data. Only 1 record in the related table so not an issue at the moment but good to know. I will try all this out. ... View more

I am currently using the FID as the PK, not a custom field. Is that already indexed? The FK is a custom integer field. It is getting filled appropriately with the FID of the origin feature ... View more

That seems to have worked.  I was able to add to the feature service and then add the relationship. I'm having some issues with working with it though.  Adding a new related record (inspection) is very clunky and the related records do not show up at all afterwards, even though they are actually there in the data table.  I'm not sure how to symbolize and use the data yet either but I will keep working on it.  If you have any pointers I'd appreciate it! Thanks ... View more