POST
|
Hi, so to add to what we already know. Currently, there is no 1:1 alternative to `UpdateWorkflow.edits`. Unfortunately, this was a needed breaking change for some bigger updates that went through with our relationship work we did back with 4.27. With this said, NOT having it documented as such is not ok, and for that we apologize. I wanted to fully confirm my suspicions so I spoke to a member on our development team regarding your approach with using `rootFeature`. Although undocumented, it will do what you need for now. The thing to consider is that this property is designed specifically to access the underlying original (root) feature that began the edit workflow you are currently in. If you have nested workflows, ie. relates, it may not access the feature you intend if you are editing in this scenario since these workflows tend to be nested. For basic updates, this should work fine. We intend on getting a better alternative to this for our next release.
... View more
03-01-2024
10:29 AM
|
0
|
0
|
472
|
POST
|
@JasonDoingMaps yes, you're correct. I meant to state that we didn't mean to keep this out of the doc. It was inadvertently missed when some updates were made. This should be fixed. As for the underlying issue that you are asking about, ie. what are you now supposed to use in its place? There is a way to do this, but that too wasn't publicly documented. I will be in touch shortly to get some more info to you as I had to confirm some things on our end as well. Again, sorry for the confusion. We'll get it squared away and make sure you have something to work with.
... View more
02-27-2024
08:17 AM
|
1
|
0
|
516
|
POST
|
This was a mistake on our end. We did document when we deprecated CreateWorkflowData.edits at 4.23. To instead use CreateFeaturesWorkflow.pendingFeatures to access edits made to the workflow data .https://developers.arcgis.com/javascript/latest/4.24/#deprecated-classes-properties-methods-events. I apologize, and agree that this is very confusing. The documentation will be fixed asap as this cannot go as-is. In the meantime, I'm working on getting something to help get you on your way. I just wanted to let you know this omission in doc was not intentional and we'll get it straightened away as a priority. Sorry for all the confusion. I'll post back as soon as I clarify what you need to do moving forward until we get that doc updated publicly.
... View more
02-26-2024
06:53 PM
|
2
|
1
|
560
|
POST
|
@LefterisKoumis I agree that it would be easier to read if broken out to a separate file. I plan on updating that sample to reflect the use of `editableExpression` as opposed to `editable` and will see if this is doable at that time. Thanks for the suggestion as I'm sure you are not the only one that is interested in seeing how this can work. - Heather
... View more
11-08-2023
05:19 AM
|
0
|
1
|
348
|
POST
|
@LefterisKoumis to clarify further on your questions, * We do have it documented, it's just not as clear and easy to quickly find as I think it should be. The web map specification has a blurb about it at https://developers.arcgis.com/web-map-specification/objects/formFieldElement/, in addition, if you look at this sample https://developers.arcgis.com/javascript/latest/sample-code/widgets-featureform-async/ it has it written in the description. I think it should be easier to find so will add an additional notice in the actual API reference. Regarding the above referenced sample, take note that all field elements that reference a `valueExpression` have editable set to `false`. This is a requirement for working with valueExpressions. * When the `formInfo` was initially implemented, we did not have support for calculations. It was very basic. You could show fields or groupings of fields. The fields could be referenced and you could control whether or not you want to require or make them visible or editable with a simple boolean. This is where the original `editable` and `required` fields were used. These properties were carried over from the legacy FieldConfig class that has since been removed in favor of using the FieldElement. With the advancements made in the form to support calculations for field visibility, editability, requirements, and value expressions, we decided to deprecate the older properties of `editable` and `required` in favor of working directly with their expression. We still honor the deprecated properties for those older maps created before this affect took place. Moving forward though, any new web maps that get written out with form configurations will reflect the expressions Although you may be able to set editableExpression directly to false, it is not the tested and recommended way using a named expression. We recommend setting it to an actual expressionInfo which returns a value of false. I know that that can be cumbersome for small booleans, but just wanted to make sure you were aware of this if you notice any weird behavior. * You asked about "after you create or edit a feature, it would be great to return the editor to its original state and stop the create/edit of other features." This is a result of some worfklow refactoring that needed to happen to support the feature to feature relationship editing. It does not break, but can be irksome if not expecting the UI update. If you click on the back arrow, it should take you to the initial state. We intend on addressing this for the next release. I intend on getting this documentation cleaned up based on some recent feedback, this including removing the deprecated `editable` property on the FieldElement. Thanks again for the input, and please reach out if you have any additional questions. -Heather
... View more
11-02-2023
01:09 PM
|
0
|
1
|
540
|
POST
|
Hi, you should be able to edit GeoJSONLayers using the editor. I don't know the extent to how you are working with the layers and how you are adding them, (ie. feature collection or referenced by URL), but here is an app showing how to use a GeoJsonLayer referenced by URL and accessed in the Editor. The documentation needs to be updated to include this layer type for the Editor.layerInfos. We will make sure to include that in the next doc update.
... View more
07-28-2023
01:58 PM
|
0
|
0
|
1000
|
POST
|
This has been a back and forth discussion as to the level of what is needed when documenting this. Your question conveys the need to provide additional context. I'll make sure to take your info and let others involved in this know that it is something we should look into further. Thanks again and hope everything works out nicely.
... View more
07-28-2023
01:03 PM
|
0
|
0
|
859
|
POST
|
Hi, the Webmap version property defines the version of the saved webmap. This version updates every four months (give or take), you should notice that it updates when ArcGIS Online has its update. The latest AGO release in June of this year writes out webmaps with the latest version of 2.28. The version property is required as it's used by other apps working with the webmap. As for your second question on setting a version number from a custom tool which generates webmaps, as long as your tool follows the spec and adheres to this requirements, it should work as expected. So if you are currently using your tool to generate webmap json, the version number should reflect the latest release, as the spec will adhere to what is specified for this release. Hope this can help.
... View more
07-27-2023
07:27 PM
|
1
|
0
|
873
|
POST
|
Hi, we have logged this as BUG-000157217, it took some sleuthing but have determined a fix and plan on addressing this for 4.27.
... View more
05-11-2023
07:02 PM
|
2
|
0
|
617
|
IDEA
|
Thanks for the idea, we realize this is important and are looking into getting this added in the near future.
... View more
10-21-2022
10:24 AM
|
0
|
0
|
1188
|
POST
|
Hi Tyler, thanks for the feedback. Yes, we intend on adding this functionality to 2d/MapView in the upcoming 4.25 release. This is slated for October time frame. Hope this helps. Heather
... View more
07-19-2022
01:51 PM
|
1
|
0
|
1213
|
POST
|
Hi David, We are actively working on improvements to the FeatureForm (which is what the Editor is using). If you could provide a repro app showing this issue, it would definitely help us try to determine where the exact issue may be occurring. It very well be addressed already with our next 4.24 release. Thanks, Heather
... View more
06-16-2022
09:42 AM
|
0
|
1
|
441
|
POST
|
Hi, would it be possible to share a repro of what you are seeing? Does it only start with 4.23? Sounds like you narrowed it down to only coded value domains?
... View more
05-04-2022
09:40 AM
|
0
|
1
|
725
|
POST
|
The property is hidden for a reason. You can use it if it works for now, but there is no guarantee that it won't be changed later on. We provided the event to get to the records so that you don't have to do this. I don't know the reasoning for not using this. Perhaps there is a use case that wasn't considered that needs to be, otherwise I would suggest the event as there is no support for undocumented properties, nor a guarantee that they won't change in any upcoming release.
... View more
03-30-2022
09:21 AM
|
0
|
1
|
2271
|
POST
|
Hi, this is actually working as expected. If you have null values within your field. By default, it is not supposed to show a label, rather empty like you are seeing now. In 4.22, it automatically added this (this was the actual bug), if you wish to show a label, you will need to set it in the form's field input like this, input: {
type: "combo-box",
showNoValueOption: true,
noValueOptionLabel: "No value"
} I've updated the codepen with this as well, https://codepen.io/hgonzago/pen/RwxZLqB?editors=1000
... View more
03-30-2022
09:18 AM
|
1
|
0
|
562
|
Title | Kudos | Posted |
---|---|---|
1 | 02-27-2024 08:17 AM | |
2 | 02-26-2024 06:53 PM | |
1 | 07-27-2023 07:27 PM | |
2 | 05-11-2023 07:02 PM | |
1 | 07-19-2022 01:51 PM |
Online Status |
Offline
|
Date Last Visited |
07-08-2024
02:07 PM
|