Latest Contributions by MichaelLev

You wrote: "Experience Builder 1.13 will be based on the 4.28 version of the API and includes map components". I looked at "What's New in ArcGIS Experience Builder Developer Edition (version 1.13) " and I have not seen any talk about this, and I also searched the code of 1.13 and failed to detect any usage of web components. Have I missed something? What is really the current situation in 1.13? and in case I want for example to insert "coordinate conversion" widget component in 1.13, I'll appreciate info about how to do it.  ... View more

@Brian_Wilson , thanks. I deveop custom widgets on WAB and now I start moving to EXB (both Developer Edition), and the web apps are used by many users thrughout the country. I work on JS (not Python). I developed up to now one "web service" that have a log of each call and also have errlog. I also inserted in its code that every some hours it runs on pre designed "fake input" and logs accordingly.  My main work are  web apps that are run only interactively by users. I can not test them by "run test". I am already using url optional parameters to log debug info to console in key points. This is used only by me when developing or testing. What I take from you is the additional idea of inserting "traps" in the code to check the program while it is running the regular way by the users. I'll sum up: 1. I'll implant "console.assert" in key points in code to "trap" when things are not ok. This will be effective mainly when I run the web app, because users regularly do not examine the console. 2. In order to "trap" and log errors when users are running the web app, I think that "assert" is not effective, so I'll do: 2.1.  Pay attention to log all "try-catch" failures (and user command failures) to some DB (I already have such DB) to be examined by me and by the customer service from time to time. 2.2. Insert "If" blocks in key points, to "trap" unexpected behaviors log them to same DB mentioned above. 2.3 Maybe I'll use my assert function either to log to DB or throw error (which will be logged to DB). The advantage of this is that I can search for all "assert" in my code, to examine wher I do the checks. const assert = function(condition, message) { if (!condition) throw Error('Assert failed: ' + (message || '')); };   ... View more

@Brian_Wilson , I was impressed by your attitude to programming, so reading "My unit testing ..." made me request if you can elaborate on your way of testing, so I can adopt something from it. ... View more

Maybe EXB does not support exchanging 2D and 3D in same page, andthe way is that the widget will direct to a different page which has the wanted sources? I am newbie to EXB so I will be happy to know  if the above makes sense at all, and what is the solution indeed. ... View more

Thank you for the explanations and for supplying the code by its 2 phases ... View more

For map or scene defined in your portal, you set whether layers are visible or not. Maybe it'll help. ... View more

I suggest you walk by these steps: 1. Display the multipoint geometry types via graphic layer (which you'll attach to the sceneView) whose elevationInfo property you'll set to "on-the-ground". 2. Use SketchViewModel whose layer property you'll set to the above graphic layer, and whose  defaultUpdateOptions you'll set thus:     defaultUpdateOptions: {         tool: "reshape",         enableRotation: false,         enableMoveAllGraphics: false,         enableScaling: false,         reshapeOptions: {             shapeOperation: "none"         },         toggleToolOnClick: false     }   ... View more