POST
|
I should have mentioned this earlier but the relate is built on GlobalIDs so they are generated automatically. That was where my confusion was with it not returning anything in Pro. It should be automatic in my mind.
... View more
04-29-2021
09:20 AM
|
0
|
0
|
749
|
POST
|
We also tried that. Unfortunately the same result. Interestingly enough the rules work fine with Field Maps & Survey123. It's only in Pro where the rule doesn't return anything on insert. I'm not sure what is different between the different platforms.
... View more
04-28-2021
09:23 AM
|
0
|
0
|
755
|
POST
|
Hello! I have an issue with related records on insert. TrafficSigns and TrafficSignsWorkOrder are the tables i am working with. I have a rule in TrafficSignsWorkOrder to pull the AssetID from TrafficSigns on insert. The problem is FeatureSetByRelationshipName doesn't seem to return any related records when run on Insert. If I trigger on update the code works perfectly. But I need to trigger on insert because our crews rarely go back on edit after the initial submit. It seems there is something that prevents a related record from being returned at all on insert. Again this all works perfect on a Update. But i need it to work on Insert. var relatedTrafficSigns = FeatureSetByRelationshipName($feature, "SDE.OWNER.TrafficSignsWorkOrder_REL", ['*'], false);
var relatedCount = Count(relatedTrafficSigns);
var relatedAssetId = "nothing";
if (relatedCount > 0) {
var relatedAsset = First(relatedTrafficSigns);
relatedAssetId = relatedAsset.AssetID;
}
return relatedAssetId;
... View more
04-27-2021
12:55 PM
|
0
|
4
|
776
|
POST
|
I can verify that I also have this issue. It seems to be just blank squares for me as well.
... View more
02-25-2020
02:42 PM
|
1
|
3
|
1397
|
POST
|
I have not been able to find anything for fixing this short of adding the deleted fields back or republishing the service. Both of which are unacceptable fixes in my opinion. I would open a support ticket and see if there is something they can do.
... View more
01-14-2020
08:31 AM
|
0
|
1
|
3978
|
POST
|
Unfortunately we had to republish the layer to fix this so I don’t have a broken example at the moment. I can verify we did not have a Def Expression set on the item. Next time it happens I will try and reach out with an example.
... View more
10-17-2019
05:46 PM
|
0
|
0
|
1776
|
POST
|
Did anyone every figure out a solution for this error? We have ran into this on multiple occasions and have not been able to fix it short of republishing the entire layer (not ideal). There is no way to reliably reproduce it. But it does happen.
... View more
10-17-2019
05:08 PM
|
1
|
1
|
3978
|
POST
|
Did anyone every figure out a solution for this error? We have ran into this on multiple occasions and have not been able to fix it short of republishing the entire layer (not ideal). There is no way to reliably reproduce it. But it does happen. And there is no def expression on these layers for me.
... View more
10-17-2019
05:06 PM
|
0
|
0
|
1776
|
POST
|
Anybody? This has to be a bug. Unless I am missing something huge.
... View more
12-18-2018
05:32 PM
|
0
|
0
|
1135
|
POST
|
I am using a script to recursivly unshare all items in an AGOL users content and I am using item.share(False, False, None, False). However after it runs the sharing on the item remains shared everyone true. Any ideas? It seems to be having trouble with items shared everyone.
... View more
12-18-2018
09:17 AM
|
1
|
3
|
1267
|
POST
|
Thanks for the advice. For our particular workflow we were wanting to avoid re-configuring all of the apps, web map, popups, etc to use the new field. That is why we named it exactly the same. We ended up recreating the view in question as this was easier then making a field with a different name. Thanks!
... View more
11-28-2018
05:23 PM
|
1
|
0
|
2608
|
POST
|
Well the problem for me in this instance is the field in question already existed. The field was deleted and then re-added with a different field string length but had an identical name to the previously deleted field. So the field shows in the view but it shows with the old length at 255 rather then the new length at 2000.
... View more
11-27-2018
04:35 PM
|
0
|
3
|
2608
|
POST
|
We have a Feature Service in ArcGIS Online that has a field called "Description". This field had the default 255 string length. We also have a few different layer views referencing this item with different options and filtering turned on. We recently had to increase this field length to 2000. What we did was create a temp field and then calc the values of "Description" into this temp field. We then deleted and re-created the "Description" field and calc the values back into it. The problem is all the layer views referencing this feature service still have the length set at 255. Even though the original service now shows 2000 for the field length. Is there any way to force the update of the layer views service definitions to reflect the length update? Thanks, Isaiah
... View more
11-27-2018
02:36 PM
|
0
|
5
|
2778
|
POST
|
Well that's pretty simple! Honestly I don't think there is any reference in the api docs to that being an option anymore. In the constructor section of the Legend Widget there is no reference that I can find. But I am glad it is still there. Thanks Robert! I'll give that a shot.
... View more
01-25-2018
08:25 AM
|
0
|
0
|
1323
|
POST
|
Is there a way to render the Legend widget outside of the mapview in the 4.x api? For instance in the 3.x api I was able to place the legend in a modal because you had more control over where it was placed in the dom. But it seems here I can only add it to the map view via the ui.add() method. Any help would be greatly appreciated. Thanks, Isaiah Aguilera
... View more
01-25-2018
08:08 AM
|
1
|
2
|
2081
|
Title | Kudos | Posted |
---|---|---|
1 | 11-28-2018 05:23 PM | |
1 | 10-17-2019 05:08 PM | |
1 | 02-25-2020 02:42 PM | |
1 | 12-18-2018 09:17 AM | |
1 | 01-25-2018 08:08 AM |
Online Status |
Offline
|
Date Last Visited |
04-29-2021
12:06 PM
|