Latest Contributions by Bud

On closer inspection, it looks like ArcGIS Pro is having difficulty with the geodatabases in that particular folder. For example, it's only showing one of two file geodatabases, which is incorrect. To prove the point, I created a new folder with a new mobile geodatabase. ArcGIS Pro is able to see that mobile geodatabase without issue (and export the table): Bud_1-1674626993864.png So something else is going on. Esri, feel free to delete this idea. ... View more

@HannesZiegler  Yes, I think this is right: Or are you looking for a similar property, but for accessing and manipulating the actual curve information rather than just confirming its existence? In hindsight, my wording wasn't great. ... View more

Thanks @KoryKramer. The use case stems from this scenario: One-to-many join - editing duplicate input table rows. Essentially, after every cell edit, the other duplicated rows become out of date, which is confusing to look at. I'd rather refresh regularly so that I'm seeing up-to-date data. ... View more

@KoryKramer  Are either of you seeing a scenario where the table Refresh is not available when you are not editing? I suppose not. Why not make the refresh button available all the time, even when editing a cell? If we were to hit the refresh button when editing a cell, then it could save & refresh all in one action. That would avoid the need for an extra click (clicking away from the edited cell to stop editing). ... View more

@JoshuaBixby  Good idea. I took an extreme approach by removing all indentations and line breaks: WITH RECURSIVE cte AS (SELECT 2023 AS year_ UNION ALL SELECT year_ + 1 FROM cte WHERE year_ < 2023 + (10) -1) SELECT row_number() over (ORDER BY cte.year_, amount) as OBJECTID, cte.year_, p.amount FROM cte LEFT JOIN Projects_MobileGDB p ON cte.year_ = p.year_ Unfortunately, I'm still seeing the same issue. The name gets cleared when I paste in the SQL. ... View more

For what it's worth, I tried copying the table to a mobile geodatabase (since mobile geodatabases have full SQL support, unlike file geodatabases). Then I created a view that dynamically generates filler rows for the missing years: WITH RECURSIVE cte AS ( SELECT 2023 AS year_ UNION ALL SELECT year_ + 1 FROM cte WHERE year_ < 2023 + (10) -1 ) SELECT row_number() over (ORDER BY cte.year_, amount) as OBJECTID, cte.year_, p.amount FROM cte LEFT JOIN Projects_MobileGDB p ON cte.year_ = p.year_ I was able to successfully create the view. And even add the view to the map. The filler rows were viewable in the attribute table, as expected. But I wasn't able to create a chart from the view. I'm not sure why. I used the same steps that I used for the table's chart, but when I did it for the view, a chart wasn't shown in the chart window. Instead, this message was shown: "No data is available to display due to empty data field(s) and/or combination filters." So I wasn't able to get the view idea working. Idea: Create chart on mobile geodatabase view Here's the SQL source: SQLite Oracle (untested) SQL Server (untested) PostgreSQL (untested)   Edit #1: I tried creating a simpler view: SELECT * FROM TABLE. But I wasn't able to create a chart on that view either. Edit #2: BUG-000155377: ArcGIS Pro: Unable to create a bar chart on a database view created in a mobile geodatabase. “One thing i noticed is that other charts (ex: Line and Scatter Plot charts) work fine. So the issue is mainly with Bar charts.” Esri Canada Case #03249403 Edit #3: Idea: Bar Chart — Set min/max x-axis bounds using calculated values; fill in gaps with empty bars ... View more

@Luke_Pinner and @Andrew-Bowne  Regrading your comments about unversioned enterprise edits not having a discard edits option: It looks like that functionality is planned in a future version of ArcGIS Pro: ArcGIS Pro Roadmap - July 2022 Near-Term (next release or two) Discard for non-versioned editing –support of workflows similar to those implemented in ArcMap for editing non-versioned data. When implemented, edits against non-versioned data will not be written directly to the database, giving the user the ability to discard edits before committing. Related: Pro Roadmap - Non-versioned Editing: “Ability to undo and/or discard edits before committing” ... View more