nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Icon is not showing for a file with Uppercase extension in case of ProCustomItem used for Plugin data source

RITASHKOUL

I have created a ProCustomItem to support a new data format by applying a plugin data source.

Now, if the file extension is in lower case, the icon is visible for the file, but if the file is in upper case, the icon is not visible for the file with the same extension.

I've included both working and non-working cases for the same file extension having lower and upper cases resp.

Icons.png

gis-for-qi-in-healthcare-twitter-1200x678.jpg

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

UmaHarano

Hi,

Just a few questions to clarify the issue -

1. Does your custom item have a file extension of gsi?

2. On disk, if the file is .GSI, then it doesn't show up in Pro with the corresponding file image. If on disk, the file is .gsi, then it shows up in Pro with the corresponding image. Is that correct?

3. In config.daml file of your add-in, can you please send me the fileExtension attribute value?

Thanks!

Uma

RITASHKOUL

1. Yes extension is gsi

2. Yes

3. <categories>
<updateCategory refID="esri_customItems">
<insertComponent id="GsiProCustomItem" className="GsiProCustomItem">
<content displayName="GsiProCustomItem" fileExtension="gsi" isContainer="false" keywords="GsiProCustomItem" contextMenuID="GsiProCustomItem_ContextMenu">
<filterFlags>
<type id="File" />
</filterFlags>
</content>
</insertComponent>
</updateCategory>
</categories>

@UmaHarano

@UmaHarano wrote:
Hi,
Just a few questions to clarify the issue -
1. Does your custom item have a file extension of gsi?
2. On disk, if the file is .GSI, then it doesn't show up in Pro with the corresponding file image. If on disk, the file is .gsi, then it shows up in Pro with the corresponding image. Is that correct?
3. In config.daml file of your add-in, can you please send me the fileExtension attribute value?

Thanks!
Uma

Wolf

According to the ProConcept document for Pro SDK Custom Items this appears to be 'by design'.

ProConcepts Custom Items · Esri/arcgis-pro-sdk Wiki (github.com)

File extensions specified in the config.daml are case sensitive, hence only files with file extensions that are matched using a case sensitive compare will work.

I am not sure of the reasons behind the reasons behind this limitation.

RITASHKOUL

Any workaround for this?

@UmaHarano @Wolf

UmaHarano

I am able to reproduce this issue too. It sounds like a bug - I will report this to the dev team. Thanks for reporting this.

In the meantime, can you please try this by matching the extension name (case) with what you have in the config.daml fileExtension attribute value?

Thanks!

Uma

RITASHKOUL

Ya so whatever case (for me mostly lowercase) and same in config.daml that is working fine. Its just now upper case scenario not working.

@UmaHarano

RITASHKOUL

@UmaHarano One more that I think is related to this if adding your own context menus on the custom item that is also not working on the file with upper case extension

UmaHarano

I can confirm that this issue is fixed in ArcGIS Pro 3.4. This was released on November 7th. Thanks!

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.