|
IDEA
|
Edited. It seems there is a bug in ArcGIS Pro 3.0.3. I tried to repeat my steps, but I got the same error you did when adding the view to the map: Failed to add data, unsupported data type. An invalid SQL statement was used. Workaround: Create the tables in a FGDB, but then copy the tables to a new FGDB (using right-click copy/paste in Catalog). In the new FGDB, I'm able to create the view, add the view to the map, and open the attribute table. Does that workaround work for you? Note: The bug doesn't appear to be specific to the INNER JOIN view we're testing. I got the same error when creating a simpler view: select * from table_a Related: Bug: View on FGDB standalone table — can't add view to map
... View more
01-17-2023
07:29 AM
|
0
|
0
|
3524
|
|
IDEA
|
Edited: For Model Builder purposes: It would be helpful if there were an OOTB geoprocessing tool for creating a new feature from scratch in an existing feature class. Or create a new row from scratch in an existing standalone table. Similar to @JohannesLindner's Python solution, but as a built-in GP tool: Is there a GP tool for inserting a row into a standalone table? We’d manually specify each of the field values, including X&Y if it’s a point FC. Standalone table example:
... View more
01-17-2023
06:40 AM
|
1
|
7
|
2822
|
|
POST
|
Is there a geoprocessing tool for inserting a new row into a standalone table? For example, in model builder, I want to add a new row to this non-spatial table: ArcGIS Pro 3.0.3 Thanks.
... View more
01-16-2023
02:57 PM
|
1
|
2
|
2157
|
|
IDEA
|
@JoshuaBixby Meanwhile, SQL joins appear to be supported in FGDB views: select * from table_a a inner join table_b b on a.id_a = b.id_b ArcGIS Pro 3.0.3
... View more
01-16-2023
11:20 AM
|
0
|
0
|
3539
|
|
IDEA
|
When I create a database view in a file geodatabase, the line breaks get automatically removed from the SQL definition. That's annoying and makes the SQL difficult to read. Could that behavior be changed so that the line breaks get preserved? Thanks. Note: ArcGIS Pro 3.0.3 currently has a known bug: It's not possible to view the SQL definition of an existing FGDB view in the view's Catalog properties. But I think that will be fixed in future versions.
... View more
01-16-2023
11:17 AM
|
3
|
0
|
635
|
|
IDEA
|
I like this idea too. I'm commenting, instead of upvoting, since the upvote button is currently disabled. Related: Kudo an idea that is flagged as Needs Clarification
... View more
01-13-2023
11:16 PM
|
0
|
0
|
2118
|
|
IDEA
|
@MarceloMarques It’s my understanding that the only thing that our DBA needs to do is run the following statement using a connection to NON_IT_USER1: GRANT SELECT ON NON_IT_USER1.FC1 TO NON_IT_USER2 WITH GRANT OPTION; I don’t think I understand why that can’t be done though ArcGIS Pro. I worked in IT previously, and often ran statements like GRANT SELECT ON NON_IT_USER1.FC1 TO IT_USER WITH GRANT OPTION; Are you suggesting the DBA had to do a one-time operation to allow NON_IT_USER1 to run GRANT SELECT ON … WITH GRANT OPTION for all tables in that owner — going forward? In other words, are you saying the DBA needs to perform a generic step before a user can GRANT SELECT ON … WITH GRANT OPTION? If so, could Esri add a “Grant [other users to create views]” column to the Privileges window in Pro, and just grey-out the checkboxes if the DBA hasn’t performed the prerequisite step yet? None of this data is sensitive. There are no security concerns about these grants. It’s just a nuisance more than anything.
... View more
01-13-2023
05:52 PM
|
0
|
0
|
3611
|
|
IDEA
|
What happens if you put a line break in the text using CTRL+Enter or something like that?
... View more
01-13-2023
04:17 PM
|
0
|
0
|
1677
|
|
IDEA
|
We have scenarios where we want to grant a different owner/user the ability to create a view on an table that our user owns. Currently, the only way to do that is to submit a ticket to the DBA which is a time consuming process. It would be better if it could be done through the privileges window in Catalog, where all other geodatabase privileges are managed. Could that functionality be added to ArcGIS Pro? Oracle 18c 10.7.1 EGDB
... View more
01-13-2023
04:11 PM
|
0
|
3
|
3646
|
|
IDEA
|
@SSWoodward Regarding, SQL for reporting and analysis on file geodatabases, I don’t think these SQL keywords work in FGDB definition queries/subqueries: CASE COALESCE JOIN NULLIF ORDER BY Here’s an example of something I want to do in a FGDB definition query, but can’t, due to FGDB SQL limitations: https://community.esri.com/t5/arcgis-pro-ideas/one-to-first-joins-control-what-related-record-is/idc-p/1239993/highlight/true#M22488 Works for SQLite/mobile geodatabases, but not file geodatabases: roadinsptable.objectid IN (
SELECT objectid
FROM roadinsptable r2
WHERE r2.asset_id = roadinsptable.asset_id
ORDER BY date_ DESC, condition DESC
LIMIT 1
) I’m aware that FGDB SQL doesn’t have LIMIT, not even in the FGDB API. There are likely other ways to accomplish it using SQL, without LIMIT, in databases that have full SQL support. But those alternatives wouldn’t be possible in FGDB definition queries due to the limited FGDB SQL. Part of the problem is that I’m not actually sure if SQL for reporting and analysis on file geodatabases actually pertains to the FGDB API. It’s a confusing page in a confusing place with no context. Edit: Here's another example of the useful stuff we can do in geodatabases like enterprise and mobile, but not in file geodatabases: Force bar chart to show missing years within 10-year range (system year + 9). The queries generate filler rows so that there are rows/bars for each year in the 10-year range.
... View more
01-12-2023
05:44 PM
|
0
|
0
|
3572
|
|
POST
|
If an idea has been flagged as Needs Clarification, then users can’t kudo the idea when it’s in that state:
https://community.esri.com/t5/arcgis-pro-ideas/save-join-for-recall/idc-p/1247706
I like that idea, understand what the person is asking for, and want to upvote it. But I can’t because the upvote button is greyed-out. And I likely won’t remember to go back upvote it — when it eventually gets changed to open.
In my opinion, just because Esri is looking for more information, it doesn’t mean the rest of us should be prevented from upvoting it.
Could that behavior be changed?
Thanks.
... View more
01-12-2023
12:37 PM
|
9
|
9
|
5112
|
|
IDEA
|
For cases when we get errors in ArcGIS Pro: It would be helpful if there were a way to copy the error text to the clipboard from the error dialog. Copying the text would make googling and submitting cases to support more convenient. Otherwise, we need to manually type out the error text, which is time consuming and error-prone. Especially for error messages that are longer than the one in the screenshot and for error messages that have lengthy error codes/numbers. ArcGIS Pro 2.6.8
... View more
01-10-2023
08:40 AM
|
1
|
1
|
861
|
|
BLOG
|
I wonder how ThomasColson’s technique would work for Oracle geodatabases, since the DEFINITION column is stored as a CLOB, not text (but available as text in a view). I guess we could just convert our modified XML to a CLOB using an SQL query, then use SQL to UPDATE the table value?
... View more
01-06-2023
06:28 AM
|
0
|
0
|
563
|
|
BLOG
|
As a token of appreciation for the thousands of hours these kind people have spent helping Esri customers, could Esri do something like offer the MVPs free Esri software? Something significant, such as a free ArcGIS Developer license, which is otherwise unaffordable for personal use. Idea: Thank MVPs by giving them ArcGIS Developer license
... View more
01-05-2023
11:38 AM
|
14
|
0
|
50221
|
|
POST
|
When can we expect the ArcGIS Pro Roadmap to be published for 2023? Looking forward to seeing what's coming.
... View more
01-05-2023
10:30 AM
|
0
|
1
|
973
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2026 02:12 PM | |
| 1 | 03-19-2026 11:42 AM | |
| 1 | 06-03-2026 04:02 AM | |
| 1 | 03-18-2026 07:08 PM | |
| 2 | 07-08-2026 01:29 PM |