Latest Contributions by DavidColey

Update. So it turns out that the Feature Info Widget DOES display complex Arcade expressions as part of the display, but only for small datasets.  I do not know what the limit is, but it is certainly less than the 2500 zoning records that I am working with.   So something like this: var newBuffer = FeatureSetByName($map,"County Zoning");//need a feature //var newBuffer = $feature; //need a feature var buffResults = false; //need a bool function getArea(){ if ($feature.zoningcode != 'MP' && $feature.zoningcode != 'SARASOTA' && $feature.zoningcode != 'NORTH PORT' && $feature.zoningcode != 'VENICE'){ BufferGeodetic($feature, 2, 'meters'); } else { $feature.zoningcode; } } var myBuffer = getArea(); if (myBuffer == $feature.zoningcode){ buffResults = false; } else { buffResults = true; newBuffer = myBuffer; } var myCen = Centroid($feature); var onezoning = Intersects($layer, myCen); var allzoning = Intersects($layer, newBuffer) var oneType = Distinct(onezoning, "zoningdesignation"); var allTypes = Distinct(allzoning, "zoningdesignation"); var zoning_count = Count(allzoning); var inizt = ''; var znlist = ''; function GetInitDomainDct() { var dom = Domain(onezoning, "zoningdesignation"); var cvs = dom["codedValues"]; var dct = {}; for (var i in cvs) { var cv = cvs[i]; dct[cv["code"]] = cv["name"]; } return dct; } var rt1 = GetInitDomainDct(); function GetDomainDct() { var domAll = Domain(allzoning, "zoningdesignation"); var cvsAll = domAll["codedValues"]; var dctAll = {}; for (var j in cvsAll) { var cvAll = cvsAll[j]; dctAll[cvAll["code"]] = cvAll["name"]; } return dctAll; } var rtall = GetDomainDct(); for (var k in oneType){ inizt = rt1[k.zoningdesignation] + TextFormatting.NewLine; } for (var m in allTypes) { znlist += rtall[m.zoningdesignation]+ TextFormatting.NewLine; } var munZone = 'Marine Park and Municipality zoning areas are too complex to list adjancent zoning . . .' var newList = ''; newList = Trim(Replace(znlist,inizt,'')); if (buffResults == false){ return munZone; } else { return newList; }   Where I am getting at coincident polygons to return information on them (but not the selected polygon, and I have to pre-filter out super-complex large polygons that absolutely kill the return time) - works just fine in the map.  BUT: for the Feature Info in EB, if I want a return there is some limit on how many records are in the feature set that can display in a list like I show above. I don't know what that limit is, but it is less than 2000.  Maybe this can be addressed for the Online version at some point?   Otherwise, maybe there is some fetch limit or something in EB Dev Feature Info that can be bumped up somewhere? @RobertScheitlin__GISP  @KenBuja  @TonghuiMing  @ShengdiZhang  @XanderBakker      ... View more

Hmm, sorry all.  I somehow missed the 'Related Posts' above stating that there is a compatibility issue with complex arcade being returned as a result in the Feature Info.  Apparently still an issue at this 1.8 release.  It will be helpful when either this is addressed or maybe somehow the List widget can return the map popup as an option . . .   ... View more

Update: Here is an example:   The Adjacent Zoning Descriptions is a list generated by buffering the feature and returning the features that intersect the buffer as a list. Why wouldn't the Feature Info widget return the Arcade-generated list the same as the Map Info window?? It would seem to me that the Feature Info Widget would certainly recognize the $feature profile that is being used. @RobertScheitlin__GISP  @KenBuja  ... View more

Hi @babarsac - so for the /client install, no issues using the above workflow at steps npm ci and npm start from the .../client directory? ... View more

Update.  I reverted back to my last \latest node js build, 14.18.1 that I am using with with EB 1.7.  I did the re-install without the 'Choclatey' option, because I'd never checked that option before when installing node js. Same issues on my client install from client directory, even when I run the command prompt as an admin.  So I guess I'll go try the 14.15.4 build  ... View more

Ok thanks for that Robert ... View more

@TonghuiMing , I can echo what both @babarsac and @RobertScheitlin__GISP have found.  My environment is the same as Robert in terms of Windows OS and Node.js I do have Visual Studio Code installed. I did try "...Or maybe you could try clearing the cache, restart from the beginning from npm ci > npm start, and see if the problem occurs...." earlier, same results: - lots of deprecation with the npm ci from the /server directory requiring npm audit fix --force to fix - none of the node_modules install from the npm ci from the /client directory. I did physically copy the node modules from my 1.7 directory to the 1.8 directory and now the /client npm start runs without issue -  but I have not tried to perform any tasks as of yet, as a physical copy does not seem to be prudent.  It was just a test ... View more

Ok thanks for that @RobertScheitlin__GISP.  It would appear there are others having similar issues, e.g  https://community.esri.com/t5/arcgis-experience-builder-questions/exp-builder-1-8-client-error-with-happyplugin-path/m-p/1165747#M4205 For the time being, I copied all of the modules from the 1.7 version at my C:\ArcGISExB17\client\node_modules\ directory into the 1.8 version.  The npm start for the client now runs without error, but we'll see if there are issues with widget builds and/or EB build deployments. @PeterK  @KenBuja   ... View more

Hello @Jianxia  - Before I upgraded EB1.7 to EB1.8, I ran an update to my node js environment to v16.14.2.  I then ran the client install from the /server directory and launched the app at https://localhost:3001/.   I then ran the client install from the /client directory and it is returning a whole host of errors: npm ERR! code 1 npm ERR! path C:\ArcGISExB18\client\node_modules\node-sass npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js npm ERR! Building: C:\Program Files\nodejs\node.exe C:\ArcGISExB18\client\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! gyp info it worked if it ends with ok npm ERR! gyp verb cli [ npm ERR! gyp verb cli 'C:\\Program Files\\nodejs\\node.exe', npm ERR! gyp verb cli 'C:\\ArcGISExB18\\client\\node_modules\\node-gyp\\bin\\node-gyp.js', npm ERR! gyp verb cli 'rebuild', npm ERR! gyp verb cli '--verbose', npm ERR! gyp verb cli '--libsass_ext=', npm ERR! gyp verb cli '--libsass_cflags=', npm ERR! gyp verb cli '--libsass_ldflags=', npm ERR! gyp verb cli '--libsass_library=' npm ERR! gyp verb cli ] npm ERR! gyp info using [email protected] npm ERR! gyp info using [email protected] | win32 | x64 ........   npm ERR! gyp verb find VS not looking for VS2013 as it is only supported up to Node.js 8 npm ERR! gyp ERR! find VS npm ERR! gyp ERR! find VS msvs_version not set from command line or npm config npm ERR! gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt npm ERR! gyp ERR! find VS checking VS2019 (16.11.32407.337) found at: npm ERR! gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools" npm ERR! gyp ERR! find VS - found "Visual Studio C++ core features" npm ERR! gyp ERR! find VS - found VC++ toolset: v142 npm ERR! gyp ERR! find VS - missing any Windows SDK npm ERR! gyp ERR! find VS checking VS2017 (15.9.28307.1622) found at: npm ERR! gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools" npm ERR! gyp ERR! find VS - found "Visual Studio C++ core features" npm ERR! gyp ERR! find VS - found VC++ toolset: v141 npm ERR! gyp ERR! find VS - missing any Windows SDK npm ERR! gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use npm ERR! gyp ERR! find VS looking for Visual Studio 2015 npm ERR! gyp ERR! find VS - not found npm ERR! gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8 npm ERR! gyp ERR! find VS npm ERR! gyp ERR! find VS ************************************************************** npm ERR! gyp ERR! find VS You need to install the latest version of Visual Studio npm ERR! gyp ERR! find VS including the "Desktop development with C++" workload. npm ERR! gyp ERR! find VS For more information consult the documentation at: npm ERR! gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows npm ERR! gyp ERR! find VS ************************************************************** npm ERR! gyp ERR! find VS npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: Could not find any Visual Studio installation to use .....   Then when I hit npm start from the /client directory, I receive the following:   C:\ArcGISExB18\client>npm start > [email protected] start > cross-env NODE_ENV=development webpack --mode development --watch node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'C:\ArcGISExB18\client\node_modules\cross-env\src\bin\cross-env.js' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } When I look in the C:\ArcGISExB18\client\node_modules directory, I can see that none of the packages installed - e.g @analytics, @babel, @esri, etc, etc.  All of the packages are in place in my ExB17 directory I had not encountered these errors before - but it looks like I need to have full Visual Studio installed?  I had not needed full VS before . . . Has anyone else experienced this behavior?  @RobertScheitlin__GISP ? @KenBuja ? ... View more

agreed . . . ... View more

Nice.  Thanks for that @LorenzMeyer1  ... View more

Geez, as soon as I posted this I discovered that the element was only erroring out in the Test and Console Log.  It works as expected in the popup . . .  ... View more

ok thanks Matt.  Can I ask if you have had any success trying to use html tags in the new rich text element?  seems something simple like this: var email = $feature.email; return { type : 'text', text : `<a href=mailto:${email}>Send email</a>` //this property supports html tags } doesn't seem to work, at least for me. @Anonymous User  ... View more

Hi @mpboyle , @Anonymous User  - I am having some trouble with the HTML editor since the March 2022 ArcGIS Online update.  When I try to edit the popup using the HTML editor, the 'OK' to save does not work - it just sits there greyed out.  Are either of you experiencing this? thanks- ... View more