Skip to content
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
This repository was archived by the owner on Jul 24, 2024. It is now read-only.

We need to pay better attention to Salesforce metadata #1783

Open
@zregvart

Description

@zregvart

This is a...


[✓] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

The problem

When using Salesforce connector we might offer the user object or field that is not usable in the context of the selected action. For instance field Name cannot be updated on the Contact object, or User object cannot be deleted via API call. This is all coded in the metadata of the objects, e.g. fields have updateable flag, objects have deletable flag.

Expected behavior

Never offer something to the user if that can lead to errors. For instance remove Contact's Name field from the data shape specification when selecting update/create or update actions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cat/featurePR label for a new featuregroup/connectorSupported camel connectorsgroup/metaService for connector meta-data and verification of connectionsstatus/never-staleMarker that this issue should not be marked as stale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions