Latest Contributions by MichailMarinakis1

Hi @dndhm, we did customize the editor tsx but not the FeatureForm. It is not recommended to customize widget's tsx 😁 and as from Release 4.27 it is officially deprecated (further information here). Just for reference, we extended the editor's tsx and we override the render function e.g.    render() { const element = super.render(); // custom code return element; }   In your case, the Editor widget exposes the featureFormViewModel but not the featureForm tsx (or does it? I couldn't find it). Normally, you may configure the featureFormViewModel.formTemplate (example here). If you want to achieve something more advanced, then I can think of these two ways forward: Instanciate a new CustomFeatureForm() which extends from FeatureForm (or from esri.widgets.Widget) and you customize the UI  (old legacy approach, not recommended) You create a new custom ui, perhaps by using calcite design components, or based on your own ui framework e.g. react, (or both 😎), and you use the featureFormViewModel to develop your logic behind the UI. You can extend the viewmodel with extra custom methods and whatnot (recommended approach, further information here) Hope i have helped 😊 ... View more

Hi @David_Brooks , thank you for the reply! The service is available to everyone, no authorization is required. We don't send the request from a browser, but from another C# Rest API, using HttpClient. In this case, we don't have cookies.  ... View more

Hi @A_Wyn_Jones , thanks for the idea! The NAS is not using DFS. Apparently there is a High Availability NAS package? something like that.    ... View more

Hi @A_Wyn_Jones , thanks for the fast reply!  We are using web adaptor and the config store is in internal shared folder on a NAS system, highly available.  Turning on the debug logging might be a good idea but we don't know when the issue is happening so we will have some trouble with space for the logs... I will see what we can do about this. ... View more

Perfect! thank you again for the prompt response. ... View more

I have a following up question 😃 Normally, using custom widgets, we were able to extend existing esri widgets to custom ones. A sample of the code is below: import { subclass } from "@arcgis/core/core/accessorSupport/decorators"; import Editor from "@arcgis/core/widgets/Editor"; import { CalciteFlowItem } from "@esri/calcite-components/dist/components"; @subclass("app.widgets.ErrorReporterEditor") export default class ErrorReporterEditor extends Editor { constructor(properties: __esri.EditorProperties) { super(properties); } render() { } }   We could do the same for the "View" of the widget i.e. the tsx and/or the "ViewModel" of the widget e.g.  import { subclass } from "@arcgis/core/core/accessorSupport/decorators"; import { fetchMessageBundle } from "@arcgis/core/intl"; import SearchViewModel from "@arcgis/core/widgets/Search/SearchViewModel"; @subclass("app.widgets.GlobalSearch.GlobalSearchViewModel") export default class GlobalSearchViewModel extends SearchViewModel { private refineYourSearchMessage: string = ""; constructor(params?: any) { super(params); this.init(); } }   If we use a UI library of our choice, then are we able to do something similar?  For example, if we could not extend esri widgets in react, then do we need to recreate e.g. the Search Widget with web/react components from scratch, instead of just extending it?  ... View more

@AndyGup  we are suspecting that there is a bug with the editor widget in ArcGIS SDK for JavaScript, that impacts custom web apps and functionalities on the experience builder.  It is reproducible at version 4.26.5 but not in the 4.26.1. There are further details in the comments above.  Please let us know about any feedback! Thank you! ... View more

Nice approach! Thanks for the response  ... View more

I am having exactly the same issue with ArcGIS JavaScript 4.26.5! Did you manage to solve this?  I have noticed that they have included returnServiceEditsOption: "original-and-current-features" in the EditorViewModel.js during the applyEdits. This is the case if the feature layer is using a URL and not a portaItem? There is some logic to test if the layer is a hosted one, or in AGOL. We are using the feature layer by loading a URL since we have an standalone ArcGIS Server. We also have an enterprise Portal and load the layer again with the url. @JoseBanuelos , @ReneRubalcava , please let us know about any feedback! Thank you!   EDIT: we downgrade to version 4.26.1 and it works fine 😅 ... View more

Great, it's more clear for us now! Thank you for the response ... View more

Hi @AndyGup ,  thanks for the reply! Just to clarify, if we start to develop a new custom web app, is it OK to use esri custom widgets UI framework ? We got a bit worried with this deprecation flag at the github project 😅 ... View more