POST
|
@Jake_S- Good morning, Jake. This is what happens. I go in to make a polygon in the Web AppBuilder - I'm not using Experience Builder right now as it does not have the edit widget adequately functioning - and as I double click to finish making the polygon a table opens up for me to enter the attribute values. I begin by entering the EstbYear and other information that is relevant to the next calculation and once I do that, close the attribute table and go to the layer widget to uncheck and check back the layer in question as this refreshes the layer both the 'Age' and the other 'field' get populated , which is what I wanted. However, before your helpful hints that was not happening the 'Age' would get populated but the next calculation would not until I went back to the 'Age' field and re-added the age again. With your helpful hints, I went to the Attribute Rules window in ArcGIS Pro and reordered the 'Age' field to get populated first before the next calculation and that did it. Hope this helps, Jake. Please let me know if you need further explanation or, you need to connect with me to see it. I will be glad to show you my process. Thank you, Abi
... View more
5 hours ago
|
0
|
0
|
8
|
POST
|
@Jake_S - here is my email address. abi.dhakal@forestry.alabama.gov. Would it be possible for you to email me, please. I will be leaving in the next 20 minutes for the day, but you can email me within the 20 minutes or, tomorrow which ever suites you the best and we can go from there. I can send you a Zoom invite so you can see what I'm doing. Thank you for your great help. Abi
... View more
yesterday
|
0
|
0
|
30
|
POST
|
@Jake_S - Thank you for your diligent approach. I appreciate you taking the trouble to troubleshoot for me. Like you mention I changed the order of operation in the attribute rule and it now seems to work. I made, Order 1 to calculate Age' from the EstbYear field and then I made Order 2 to calculate the next field that succeeds that. That was really helpful. Thank you again, Abi
... View more
yesterday
|
0
|
2
|
42
|
POST
|
- I have this expression that calculates years and populates a field called 'Age'. It gets this information to calculate years from a field called EstbYear (as you can see in the expression below) that I populate with the year it was established. However, it puts the years in the 'Age' field only after the layer is checked and unchecked in the web map. With this happening, another field calculation that relies on 'Age' is not getting calculated unless I go back in and put the age manually first, before I put in the other variables for the calculation to happen This is the calculation I used which is working just fine: var currentTime = Year(Now()); var survey = $feature["EstbYear"]; // Calculate age in years var age = 0; if (!IsEmpty(survey)) { age = currentTime - survey; } return age; Is there something I am missing. Do I have to tell somewhere that the next calculation needs to double check the 'Age' field so it can calculate the next field. Do I need to put something in the arcade rule in ArcGIS Pro for the calculation to recognize 'Age' field to so it can see the 'Age' field value to do the next calculation? Thank you for your help, Abi
... View more
yesterday
|
0
|
5
|
130
|
POST
|
@XanderBakker @LukeAllen2 - I have this expression that calculates years and populates a field called 'Age'. It gets this information to calculate years from a field called EstbYear (as you can see in the expression below) that I populate with the year it was established. However, it puts the years in the 'Age' field only after the layer is checked and unchecked in the web map. With this happening, another field calculation that relies on 'Age' is not getting calculated unless I go back in and put the age manually first, before I put in the other variables for the calculation to happen This is the calculation I used which is working just fine: var currentTime = Year(Now()); var survey = $feature["EstbYear"]; // Calculate age in years var age = 0; if (!IsEmpty(survey)) { age = currentTime - survey; } return age; Is there something I am missing. Do I have to tell somewhere that the next calculation needs to double check the 'Age' field so it can calculate the next field. Do I need to put something in the arcade rule in ArcGIS Pro for the calculation to recognize 'Age' field to so it can see the 'Age' field value to do the next calculation? Thank you for your help, Abi
... View more
Tuesday
|
0
|
0
|
9
|
POST
|
@GISAdmin39 I briefly tired the Table widget and it seems to be working. However, I like the way it used to work in WAB.
... View more
|
0
|
0
|
19
|
IDEA
|
This issue becomes even more pressing considering that Experience Builder and its widgets are not yet fully functional. Compounded with the fact that Esri will discontinue support for Web AppBuilder in less than a year, the need for an import tool becomes urgent.
... View more
03-14-2024
07:00 AM
|
0
|
0
|
387
|
IDEA
|
If there's no option to import Web AppBuilder apps into Experience Builder and no support for Web AppBuilder post its discontinuation, shouldn't Esri establish a specialized support team to assist clients in manually migrating their Web AppBuilder apps to Experience Builder? Thank you, Abi
... View more
03-12-2024
11:45 AM
|
0
|
0
|
490
|
IDEA
|
If there's no option to import Web AppBuilder apps into Experience Builder and no support for Web AppBuilder post its discontinuation, will it help for Esri to establish a specialized support team to assist clients in manually migrating their Web AppBuilder apps to Experience Builder? Thank you, Abi
... View more
03-12-2024
11:20 AM
|
3
|
0
|
179
|
IDEA
|
@ChrisMyers_NewQuest @JeffPace1 - Is there not some workaround available? Is this a situation where it's simply not feasible, or is it something that could be achieved with significant effort? There must be a workaround to facilitate a smooth transition from Web AppBuilder to Experience Builder. With Experience Builder, both Esri and clients like myself are grappling with the challenge of creating apps that align with their intended purpose, much like they were designed to do in Web AppBuilder. However, with just a year left before Web AppBuilder becomes obsolete, many of the widgets in Experience Builder are either unavailable or incomplete. Looking ahead, as we approach the end of Web AppBuilder's lifecycle, there's a concern about the learning curve involved in fully implementing Experience Builder in a production environment. It just doesn't seem equitable. If there's no option to import Web AppBuilder apps into Experience Builder and no support for Web AppBuilder post its discontinuation, will Esri establish a specialized support team to assist clients in manually migrating their Web AppBuilder apps to Experience Builder? Thank you, Abi
... View more
03-12-2024
10:58 AM
|
0
|
0
|
523
|
IDEA
|
In the very near future, Web AppBuilder is slated to be replaced by Experience Builder. To ensure a smooth transition for both clients and Esri, I believe it's imperative to include an option in Experience Builder for easily importing existing Web AppBuilder applications. This functionality would seamlessly transfer all relevant widgets and settings, significantly simplifying the migration process of Web AppBuilder items to Experience Builder. Thank you, Abi
... View more
03-12-2024
10:04 AM
|
18
|
7
|
619
|
POST
|
@JeffreyThompson2- It does not look like it is available in 11.2 either. I do not see the Set Filter and Statistics in ArcGIS Enterprise. I believe this must be brought to the attention of @Jianxia
... View more
03-11-2024
11:16 AM
|
0
|
1
|
210
|
POST
|
I will have to check this out, @JeffreyThompson2 - Is this feature available in ArcGIS Enterprise?
... View more
03-11-2024
10:38 AM
|
0
|
1
|
220
|
POST
|
@Jianxia - One major concern I've noticed with the ExB app is the lack of a feature to open the attribute table of a layer directly from the layers' ellipsis menu on the map app itself – those three dots next to each layer – like what's available in WAB. In WAB, users can simply click on the layers' ellipsis and select 'View in Attribute Table'. This attribute table functionality offers various options and filters for comprehensive querying and mapping. It facilitates printing a map in a major way by enabling the end user to only print features of interest and hide unnecessary features from the printout put. This capability is especially crucial as it empowers end-users with a wide range of querying options for all layers present in the map application. Unlike ExB, where developers make assumptions about the queries clients may need and provide only pre-configured, limited options, there needs to be more flexibility. The querying process should be open, akin to WAB, allowing clients to freely choose and perform any query they desire on any available layer within the map application. This is all very fundamental for printing maps with only features of interest, as users can filter out other features to exclude from printing. Enabling an open query option within the map application would allow clients to search, export tables, or apply filters to any layers, enhancing their experience and enabling them to create custom maps efficiently. Thank you, Abi
... View more
03-11-2024
09:19 AM
|
0
|
6
|
259
|
Title | Kudos | Posted |
---|---|---|
1 | 01-22-2024 01:34 PM | |
1 | 01-22-2024 01:40 PM | |
3 | 03-12-2024 11:20 AM | |
18 | 03-12-2024 10:04 AM | |
1 | 11-20-2023 05:55 AM |
Online Status |
Online
|
Date Last Visited |
5 hours ago
|