Problems using Search with data that uses subtypes?

Mike Schonlau

22 octobre 2025 14:10

Has anyone else come across a problem configuring Search to work with data that uses subtypes? We've been struggling with that here. We replicated the data, removed the subtypes, and the Search works fine. However, that is not an option for our production data. Any suggestions? Thanks

0

• Commentaire officiel

  

  Jakob Furrer

  23 octobre 2025 11:16

  Hi Mike,

  The capability to index subtype layers has been available in VertiGIS Studio Search for over a year now. At present, we’re not aware of any open issues related to this functionality.

  That said, subtypes — especially when combined with domains — can be quite complex. To investigate your specific scenario, we’ll need more detailed information.

  Please feel free to email me directly (jakob DOT furrer AT vertigis DOT com) or contact VertiGIS Support, and include the following details:

  • Are you using the native Studio Web search integration or a search workflow?
  • Can you successfully create a search configuration for the layer(s)?
  • Has a search index (subindex) been created?
  • Are the search results incorrect or entirely missing?

  As always, the most effective way for us to troubleshoot is to have access to the layer in question, so we can analyze it directly on a developer machine.

  Best regards,
  Jakob
• 

  Jakob Furrer

  29 octobre 2025 16:45

  Hi,

  Thanks to the additional information you provided, we were able to reproduce and analyze the issue in detail.

  The configuration you shared appears correct and should generally work as expected.
  However, the problem is indeed caused by the definition of the subtypes, specifically in cases where the modelName and name attributes of the field differ:

  {
    "nullable": true,
    "editable": true,
    "defaultValue": null,
    "type": "esriFieldTypeSmallInteger",
    "modelName": "ORGANIZATION",
    "domain": null,
    "name": "organization",
    "alias": "Organization"
  }

  We’ve addressed this internally under User Story 346488: “Support indexing of feature layers with differing modelName and name field attributes”.
  The fix will be included in VertiGIS Studio Search 1.15, scheduled for release in December 2025.

  Workaround for VSS 1.14.0:
  If possible, re-publish the feature service so that the subtype field’s name matches the actual field name (organization, lowercase). This will allow Studio Search to index the layer successfully.

  Best regards,
  Jakob

  0

Vous devez vous connecter pour laisser un commentaire.