---
schema_version: "1"
id: d08c4a1c42ed75c7496b16b7c4d69fc0b54f3513ca40905360b7f5b0f90a3071
title: Troubleshooting Tips
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries-integrations/health/guides/troubleshooting-tips.md
canonical_url: https://developer.salesforce.com/docs/industries/health/guide/troubleshooting-tips.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b8ccbb64af3491f570d8500c9fdc2e9ea102b934dab34b0669636774c4ee603b
products:
  - Salesforce Healthcare API
  - Industries Integrations
---
# Troubleshooting Tips

Review these tips when you troubleshoot inbound API calls with Health Cloud Integration.

## Unable to Access AccountAccountRelation or ContactContactRelation Objects

While calling Health Cloud Integration Inbound APIs, if you’re unable to see the `AccountAccountRelation` or `ContactContactRelation` objects, verify if you have enabled the group membership settings.

To resolve this issue:

1. From Setup, in the Quick Find box, enter Group Membership Settings, and then select **Group Membership Settings**.
2. Enable the group membership settings.
3. Save your changes.

## Unable to Access a Field on an Object

While calling Health Cloud Integration Inbound APIs, the system throws an error that you don’t have field-level security enabled for a field. For example, when you try to access the `AdmissionType` column on the `CareRequest` object with field level security disabled, you get this error:

> No such column 'AdmissionType' on entity 'CareRequest'. If you are attempting to use a custom field, be sure to append the '\_\_c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

To resolve this error:

1. From Setup, open Object Manager, and then in the Quick Find box, enter the name of the object that contains the field.
2. Select the object, and then click **Fields & Relationships**.
3. Select the field you want to modify.
4. Click **Set Field-Level Security**.
5. Specify the field's access level.
6. Save your changes.

## Unable to Access the CarePlan Object

While calling Care Management Inbound API, if you receive an error response related to accessing CarePlan entities, verify if you have enabled Care Plan settings.

> sObject type 'CarePlan' is not supported. If you are attempting to use a custom object, be sure to append the '\_\_c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

To resolve this error:

1. From Setup, in the Quick Find box, enter _Care Plan Settings_, and then select **Care Plan Settings**.
2. Enable the care plan settings.
3. Save the changes
4. From Setup, in the Quick Find box, enter _Permission Sets_, and then click **Permission Sets**.
5. Select the Care Plans Access permission set.
6. Click **Manage Assignments** and then **Add Assignments**.
7. Select the checkboxes next to the names of the users you want to assign to the permission set, and click Next.
8. Optionally, select an expiration date for the user assignment to expire. For more information, see [Permission Set and Permission Set Group Assignment Expiration](https://help.salesforce.com/s/articleView?id=sf.permissions_assign_expire_how.htm&type=5) in Salesforce Help.
9. Click **Assign**.

## Transaction Rolled Back

While calling `RelatedPerson` Post resource under Admin API, if the response returns this error, verify if there is a default picklist value set. If the default value is not set, add a Unknown picklist value and make it default.

```
{
            "resourceType": "OperationOutcome",
            "issue": [
                {
                    "severity": "error",
                    "code": "exception",
                    "details": {
                        "text": "The transaction was rolled back since another operation in the same transaction failed., Required fields are missing: [SpeakingProficiencyLevel, WritingProficiencyLevel]"
                    }
                }
            ]
        }

```

To resolve this issue, add Unknown picklist values to PersonLanguage.SpeakingProficiencyLevel and PersonLanguage.WritingProficiencyLevel and make this value default.

1. From Setup, open Object Manager.
2. In the list of objects, click **Person Language**.
3. From the Contact details, click **Fields & Relationships**.
4. Click **Speaking Proficiency Level**.
5. In Values, click **New**.
6. Type the name of the new value as _Unknown_.
7. Click **Save**.

Now, you can see the new field as an option under the preferred value on a Speaking Proficiency Level record.

Repeat the same steps for the Writing Proficiency Level.

## Patient API: Failed Records

While accessing the patient API, if you receive this error response, verify if you have enabled users to add reciprocal roles.

```
{
            "resourceType": "OperationOutcome",
            "issue": [
                {
                    "severity": "error",
                    "code": "exception",
                    "details": {
                        "text": "{\n  \"failedRecords\": [\n    {\n      \"generalPractitioner\": [\n        {\n          \"message\": \"Value does not exist or does not match filter criteria.\\n\\ncommon.exception.ApiException: Value does n\"\n        }\n      ],\n      \"identifier\": [\n        {\n          \"type\": {\n            \"message\": \"Unexpected problem occurred.\"\n          }\n        },\n        {\n          \"type\": {\n            \"message\": \"Unexpected problem occurred.\"\n          }\n        }\n      ]\n    }\n  ]\n}"
                    }
                }
            ]
        }

```

To resolve this issue, follow the steps in the Enable Users to add [Reciprocal Roles](https://help.salesforce.com/s/articleView?language=en_US&id=sf.record_settings_reciprocal_role.htm&type=5).

## Administration API: PersonAccount Record Type Missing

While accessing the administration APIs, the system throws this error:

```
{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "error",
            "code": "exception",
            "details": {
                "text": "The PersonAccount record type is missing in your org. Your Salesforce admin can help with that."
            }
        }
    ]
}

```

This issue occurs when there are more than one person accounts in the org.

To resolve this issue, pass the `recordTypeLabel` in request and specify which person account the patient record must be associated with.

Example: payload.recordTypeLabel = “Patient”

For Practitioner and RelatedPerson, use `payload.recordTypeLabel` to associate the account with a recordType. The default RecordType is `PersonAccount`.

## Error is returned when performing GET call on the Location and Practitioner objects

```
{

    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "details": {
                "text": "Exception(s) were found for route(s): \n\tRoute 1: org.mule.runtime.core.api.retry.policy.RetryPolicyExhaustedException: 'until-successful' retries exhausted"
            }
        }
    ]
}
```

To resolve this issue, disable the field level security for `Contact.Gender` and `TimeSlot.WorkTypeGroup`.