Update boolean attribute about apiv3-nodejs-library

[germainvictor]

It works very well 🔥

Thank you for your reply !

[shubhamUpadhyayInBlue]

Hi @germainvictor
Can you please share some sample data from the fileUrl or the fileBody that you are passing while using the contact import endpoint?

I would like to see the structure of the data that you are trying to import.

FYI in boolean type of attributes, we expect either true or false.

Also, I assume that you have created an attribute with "category": "normal" and "type": "boolean"

Happy to help!

[germainvictor]

Hi,

Here is an example of a fileBody :

EMAIL;PRENOM;NOM;AUTO_IS_SSO;AUTO_SSO_DOMAIN_NAME;AUTO_USER_ONBOARDED_TOTAL;AUTO_ORGANIZATION_NAME;AUTO_PROJECT_IN_PROGRESS_ORGANIZATION_TOTAL;AUTO_MONTHLY_BUDGET;AUTO_LAST_PROJECT_ORGANIZATION_NAME;AUTO_LAST_PROJECT_ORGANIZATION_DESCRIPTION
[email protected];Project creator;org 1;false;;9;Matters;9;100;CFP 4 Project 2;Energy for all 2!
[email protected];Project backer;org 1;false;;9;Matters;9;100;CFP 4 Project 2;Energy for all 2!

This is the attribute AUTO_IS_SSO that I am trying to update

Also, I assume that you have created an attribute with "category": "normal" and "type": "boolean"

I confirm that the attribute is: "category": "normal" and "type": "boolean"

I contacted customer service and they told me that (but it doesn't work):

I would like to inform you that in order to update Boolean attributes, you have to use the true or false value and also add the attribute within "..".

Thank you for your help!

[shubhamUpadhyayInBlue]

Hi @germainvictor
I checked and found that there is an inconsistency on our side with the usage of boolean attributes. The solution that I suggested above works fine for the single create contact endpoint. But,

• When you use the contact import API you have to pass the values of boolean attributes as yes or no
  Example: fileBody : EMAIL;BOOL\n"[email protected]";yes\n"[email protected]";no

So, instead of passing true you will have to pass yes and for false you must pass no. It is a known issue and we would fix it on our side. Apologies for the inconvenience caused.

Do let me know in case you have any queries further.
Happy to help!