Error in "accountCreateTempate" for new custom SaaS connector

[ralph-mishiev]

Below is the content of connector-spec.json for new connector. For this connector I was trying to use accountAttributes in addition to identityAttributes for creating new account. Is accountAttributes allowed in account plan?
I am getting error below when trying to upload new connector file to tenant:

---

*Error: upload failed. status: 400 Bad Request*
*body: {"detailCode":"Bad Request","trackingId":"e05c86438353496593c075768ce3c6be","messages":[{"locale":"en-US","localeOrigin":"DEFAULT","text":"400 Bad Request: connector specification validation failed:  Schema validation error in path: [/accountCreateTemplate/fields/11/initialValue: {\"attributes\":{\"attr... did not match any of the specified OneOf schemas ...*

---

Content of connector-spec.json:

.

..
"accountCreateTemplate": {
		"fields": [
			{
				"key": "login",
				"label": "login",
				"type": "string",
				"required": true,
				"initialValue": {
					"type": "identityAttribute",
					"attributes": {
						"name": "email"
					}
				}
			},
			{
				"key": "firstName",
				"label": "firstName",
				"type": "string",
				"required": false,
				"initialValue": {
					"type": "identityAttribute",
					"attributes": {
						"name": "firstname"
					}
				}
			},
			{
				"key": "lastName",
				"label": "lastName",
				"type": "string",
				"required": false,
				"initialValue": {
					"type": "identityAttribute",
					"attributes": {
						"name": "lastname"
					}
				}
			},
			{
				"key": "approvalLimit",
				"label": "approvalLimit",
				"type": "string",
				"required": false,
				"initialValue": {
					"type": "accountAttribute",
					"attributes": {
						"sourceName": "NetSuite",
						"attributeName": "custentity_mgmt_level"
					}
				}
			},
...

[Sachin_Rajathadri]

Hi Ralph,

I have used account attribute in the AD Create account profile before.
Here’s an example

{
            "name": "givenName",
            "transform": {
                "type": "accountAttribute",
                "attributes": {
                    "attributeName": "givenName",
                    "sourceName": "Non-Employee"
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        },
        {
            "name": "sn",
            "transform": {
                "type": "identityAttribute",
                "attributes": {
                    "name": "lastname"
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        }

Question, is there a reason why you can not map that account attribute to an identity attribute and use that in your create account profile?
Also, verify if the attributeName is exactly the same as the account schema.

Thanks,
Sachin

[ralph-mishiev]

Thanks Sachin for response it it good to know that it could be done!
The only difference is the fact I am setting it up from SaaS connector config so may be there is a limitation of support from there. In the worst case scenario I can deploy SaaS connector and then configure account profile directly in the source thru API.
Reason for doing this is to prevent proliferation of identityAttributes which only used in one place as we have large number of source to source integrations.

FYI, I have also double checked attributeName is matches name in account schema for second source:)