Latest Contributions by Bud

‎02-01-2023

Esri Canada Case number #03255222 “Definition query with subquery shown as inactive (incorrect)” Bug number: BUG-000155660 Synopsis: Definition queries do not appear as active after enabling the query and reopening the definition query again. Related: Modifying existing SQL expression disables definition query

‎02-01-2023

I've been doing some testing with Esri Canada support (Case #03252485). Here's where I'm at: Unfortunately, I’m currently unable to reproduce the issue – not even with my original view – the one I used to take the screenshot that I put in the Esri Community post: https://community.esri.com/t5/image/serverpage/image-id/61266i16BFB9CD1AF2C02E/image-size/medium?v=v2&px=400 I’m not sure why I’m not seeing the issue right now. The years (field name: YEAR) in the view are being displayed as numbers, not zero, as desired. It’s frustrating that the issue is intermittent/inconsistent. I’m going to do some more testing.

‎02-01-2023

Merged from a separate idea. If I understand correctly, it's possible to set a field as read-only in the map Contents layer properties. Bud_0-1675262581749.png But it's not possible to set a field as read-only in the feature class source properties in the geodatabase. Bud_1-1675262616190.png It would be helpful if we could set fields to read-only right in the FC source. I'm aware that we can do something similar using attribute rules. But that requires custom code, adding complexity to an already heavily customized system. To me, it would be better if we could do it using OOTB functionality in the FC source properties. ArcGIS Pro 3.0.3

‎01-31-2023

Here's an example of join that passes the "Validate Join" test, but results in a broken join: Join to table with definition query — column name should get prefixed (SQL expression with subquery)

‎01-30-2023

@George_Thompson 11.0.0.3.0 looks like the geodatabase version number, not the PosrgreSQL database version number. I’m looking for the database version number, such as PostgreSQL 13.6 or Oracle 18c.

‎01-30-2023

It would be helpful if the database version number could be shown in the database connection properties in ArcGIS Pro (or a similar location). For example: Oracle 18c. I'm aware that I can query the database directly for that information using an SQL client. But not all computers/users have an SQL client. So it would be better if we could see that information right in ArcGIS Pro. Example use case: The user needs to know what the database version is so that they can know what SQL will be valid when writing a definition query, query layer, etc. Could that functionality be added? Thanks.

‎01-27-2023

@ChristopherAllen Oh, ok. Thanks. Feel free to close.

‎01-27-2023

Just a heads up to anyone reading this: We can't do division in file geodatabase views: FGDB views: Since the division operator '/' isn't supported, create a DIVIDE() function instead

‎01-25-2023

It would be great if we could create stacked bar charts in ArcGIS Pro. Like this: Bud_1-1674714058986.png Currently, I think only regular bar charts are possible. Bud_0-1674714377035.png Thanks.

‎01-25-2023

ArcGIS Pro 9.0? Isn't the latest version 3.0.3?

‎01-25-2023

I have a FGDB table that I'll use to make a bar chart: YEAR_ AMOUNT ---------- ---------- 2024 100 2025 200 2025 300 2026 400 2027 500 2028 600 2028 700 2028 800 2029 900 2031 100 Bud_0-1674711018656.png That bar chart works, but I need bars in the bar chart for each year within a range: system year + 9. In other words, I want bars for 10 years, starting with the current year (currently 2023). But in ArcGIS Pro 3.0.3, I can't control the x-axis bounds: Bud_1-1674711116851.png Ideally, I'd be able to set the x-axis min and max bounds using calculated values: Min: EXTRACT(YEAR from SYSDATE) = 2023 Max: EXTRACT(YEAR from SYSDATE) + 9 = 2032 The x-axis would have bars for all years in that range: 2023, 2024, 2025, 2026, 2027, 2028, 2029, 2030, 2031, 2032. You'll notice that 2023, 2030, and 2032 were missing from the data, but were added due to the range. It would look like this: Bud_2-1674711504800.png The x-axis bounds would be dynamic. So on January 1, 2024, the chart would automatically switch from 2023-2032 to 2024-2033. To be clear, I don't want to manually add filler rows to the table or export a copy of the table for modifying the data. I want dynamic bounds in the chart. It's important to note that all gaps need to be filled; the chart wouldn't look right if there was a gap for 2023, 2030, or 2032. I suppose the programming language for the calculated values would be Arcade. Could that functionality be added to ArcGIS Pro? Related: Force bar chart to show missing years within 10-year range (system year + 9)

‎01-25-2023

I was able to get the view idea to work in an Oracle enterprise geodatabase (18c; 10.7.1; ArcGIS Pro 2.6.8). Bud_0-1674683017445.png Bud_1-1674683112087.png Oracle: Generate rows for missing years within range (sysyear + 9) --create or replace view a_test_tbl_vw as select cast(rownum as number(38,0)) as rownum_, cast(year as number(38,0)) as year_, amount from ( select y.year, t.amount from (select extract(year from sysdate) + level - 1 as year from dual connect by level <= 10) y left join infrastr.a_test_tbl t on t.year = y.year order by y.year, t.amount ) Note: I initially had a problem when naming the column "YEAR" in the view. I fixed it by changing it to "YEAR_". EGDB view — YEAR column displayed incorrectly as zeros in attribute table

‎01-25-2023

The problem seems to be the column name "YEAR". If I change that column name to something else, such as "YEAR_", then it works fine in ArcGIS Pro: --create or replace view a_test_tbl_vw as select cast(rownum as number(38,0)) as rownum_, cast(year as number(38,0)) as year_, amount from ( select y.year, t.amount from (select extract(year from sysdate) + level - 1 as year from dual connect by level <= 10) y left join infrastr.a_test_tbl t on t.year = y.year order by y.year, t.amount ) Bud_0-1674682036610.png "YEAR" is an SQL keyword in Oracle (but using it in SQL isn't prohibited, just discouraged). Maybe that causes a problem in ArcGIS Pro? Or maybe "YEAR" is a reserve word in Pro, but not in ArcMap?

‎01-25-2023

ArcGIS Pro 2.6.8 I have an Oracle 18c 10.7.1 EGDB standalone table: Bud_1-1674680551110.png YEAR AMOUNT ---------- ---------- 2024 100 2025 200 2025 300 2026 400 2027 500 2028 600 2028 700 2028 800 2029 900 2031 100 I've created a view on the table that generates filler rows: --create or replace view a_test_tbl_vw as select cast(rownum as number(38,0)) as rownum_, cast(year as number(38,0)) as year, amount from ( select y.year, t.amount from (select extract(year from sysdate) + level - 1 as year from dual connect by level <= 10) y left join infrastr.a_test_tbl t on t.year = y.year order by y.year, t.amount ) ROWNUM_ YEAR AMOUNT ---------- ---------- ---------- 1 2023 2 2024 100 3 2025 200 4 2025 300 5 2026 400 6 2027 500 7 2028 600 8 2028 700 9 2028 800 10 2029 900 11 2030 12 2031 100 13 2032 Use Case: Force bar chart to show missing years within 10-year range (system year + 9) SQL Source: Oracle: Generate rows for missing years within range (sysyear + 9) Problem: When I add the view to ArcGIS Pro 2.6.8, the YEAR column is displayed as zeros, which is incorrect: Bud_2-1674680761134.png Whereas, ArcMap 10.7.1 displays the YEAR integers correctly: Bud_3-1674680907386.png Why is the YEAR column being displayed as zeros in ArcGIS Pro? I'm aware that views can be tricky in ArcGIS, especially when there are generated rows — rows that aren't selected directly from a table. But I believe I've satisfied all of ArcGIS' requirements for views. The view has a unique ID that is a number. And the YEAR column has been CAST as a proper integer too. So I think it should work. And the fact that it does work in ArcMap tells me that it should work in ArcGIS Pro too.

‎01-25-2023

Esri Canada Case #03248861 The following defect has been logged and attached to your case: BUG-000155584 - View on FGDB standalone table gives error “Failed to add data, unsupported data type. ” while adding to a map The current workaround is the following: 1. Sometimes if we remove the TABLE_A from the contents and then add the View1 to the map it will be successful, other times it will give you the same error. 2. If you create a NEW file geodatabase and copy the view to new FGDB it will add to the map successfully, you can then add the original VIEW from the original FGDB without issue to the map. 3. We can also copy the table to a new file geodatabase and create the same view on the new FGDB table and you can add the view without issue.

My Ideas

Latest Contributions by Bud

Re: Make definition query's toggle more intuitive

Re: Bug: EGDB view — YEAR column displayed incorrectly as zeros in attribute table

Set fields to read-only in the FC source properties, not just the map Contents layer properties

Re: If join has an error, don't create a broken join

Re: Show database version number in database connection properties

Show database version number in database connection properties

Re: Stacked bar charts

Re: ETL & File Geodatabase Views

Stacked bar charts

Re: ArcGIS Pro 9.0: How two columns of points are transferred as two fields in the attribute table of polygon layer?

Bar Chart — Set min/max x-axis bounds using calculated/sysdate values; fill in gaps with empty bars

Re: Force bar chart to show missing years within 10-year range (system year + 9)

Re: EGDB view — YEAR column displayed incorrectly as zeros in attribute table

Bug: EGDB view — YEAR column displayed incorrectly as zeros in attribute table

Re: Bug: View on FGDB standalone table — can't add view to map

Integrate ArcGIS Data Pipelines in ArcGIS Enterpri...

Send configurable email notifications from ArcGIS ...

Re: How reliable are ArcGIS Online webhooks?

How reliable are ArcGIS Online webhooks?

Sharepoint List Connector

GIS Jobs

Roads and Highways User Group (RHUG)

Local Government Solutions Users

Mapping and Charting Enterprise Databases

ArcGIS Arcade