Line Item custom property error

Develop, Build & Integrate APIs & Integrations
1

I had a unique value custom property created in line item “my_custom”. I deleted it through API and I’m tying to create it again through API but I’m having this error: “Can’t update existing non-unique property to be unique”. When I search and when I try to edit the property I have this error: “No property named ‘my_custom’ exists.”. When fetch all the properties through API this property is not on the list and there is no place to manage the line items properties on UI.

2

Hey, @RAraujo0 :waving_hand: Thank you for posting this question.

I did a bit of digging in our internal resources. Here’s what I found — Once you create a property that has a unique value equal to false it is not possible to convert it to true. At this time, you’ll need to create the property again but with a different internal value — my_custom2 or something else. You can use the same label “My Custom” but not the same internal value.

Best,

Jaycee

3

Hello @Jaycee_Lewis Thank you for your response. Am I not able to delete this custome property via API “DELETE /properties/line_items/{}”?

4

Hey, @RAraujo0 :waving_hand: That is correct. It’s because of the `uniqueValue` flag. Once deleted, it lives in the recycling bin for up to 90 days. But in this case, it cannot be fully purged, preventing you from reusing the internal value. We can find it by making a request like this:

GET {{API URL}}/crm/v3/properties/line_items/my_custom?archived=true

Talk soon. — Jaycee

5

OK, but why can’t we manage the custom properties from Line Items through UI like we can with deals and companies for example? In UI I can archive and delete it from archived for deals properties but not for line items.

6

Hey, @RAraujo0 :waving_hand: There is not a public document that details this distinction. I understand what you are after and why it would be useful. But at this time we are limited to the available options. I understand this is not the answer you are wanting. I know that there is work on this and related challenges internally, but I do not have anything I can share at this time. The dev changlelog will be our best source of truth for updates like this.

Best,

Jaycee