> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/tutorials/resourcetype-and-resourcediscriminator.md).

# resourceType and resourceDiscriminator

Starting with Collibra version 2024.10 we deprecated the `resourceType` field that is part of `Resource` and `ResourceReference` objects and their accessor methods, in favor of `resourceDiscriminator`.

Both fields have the same logical value but different data types:

* `resourceType`:
  * Returns an `enum` value.
  * Returns `BaseDataType` for traits and any newly added resource types.
* `resourceDiscriminator`:
  * Returns a `string` value.
  * Returns `Trait` for traits.

## Backward compatibility

The introduction of the `resourceDiscriminator` field is necessary to ensure backward compatibility while we add new resource types as part of the evolution of the platform. Adding new values to an `enum` list is not considered backward compatible as it poses challenges to existing integrations that must regenerate their client libraries or fail to recognize the newly added values.

The deprecation of the `resourceType` field means your current applications continue to work without the need to replace the deprecated field with the new field until you are ready to do so.

{% hint style="info" %}
Some APIs may still expect `resourceType` as an input field without having an alternative available as we are in the process of updating them. Once the updates are complete, you should also update your integrations to use `resourceDiscriminator`.
{% endhint %}