• Hi,

    Is there any evolution on the way custom fields are stored in the database so that we can use, for example in a Select, a text with commas?

    We’re using custom fields to store course names, and some are long and with commas. I couldn’t found a way to do it yet.

    Thanks.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Jay

    (@bluejay77)

    Hi @alvarogois,

    We’re using custom fields to store course names, and some are long and with commas.

    I’m not sure what you mean by “Store Course Names”. Are these custom fields for Jetpack CRM contacts?

    In general, you can access the custom field editor in the Custom Fields section of CRM Settings. You can check out our knowledgebase article for more information:

    https://kb.jetpackcrm.com/knowledge-base/how-to-use-custom-fields-in-jetpack-crm/

    If you’re referring to something else, would you please specify where in Jetpack CRM you want to add the custom field to? Is it to a Company, Contact, Transactions, Invoices, Quotes, or something else?

    Thanks!

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Hi Jay,

    Sorry if I was not clear. Yes, I mean contact custom fields.

    So, we created a contact custom field named Course. It’s a select field, with course names. The problem is some course names have commas. And the CSV format of the custom field prevents the use of commas in the field content, right?

    We used JCRM in another similar project and tried all sorts of safe characters to isolate the commas, to no avail.

    That’s why I’m asking of there was any changes that allow us now to use commas in the Select field options.

    Thanks.

    Jay

    (@bluejay77)

    Hi @alvarogois,

    Thank you for explaining further. It sounds like you’re adding selectable options in a contact custom field like this: 'first, course', 'second, course', 'third, course' and seeing it concatenated as six different selectable options instead.

    Unfortunately, these “CSV field” options are intended to be separated at comma, so there is no easy way to add a selectable option that includes a comma as a part of the name. As an alternative, I suggest replacing a comma with anything else, such as a semi-colon (;) or hyphen (-).

    I’m sorry we don’t have better news. Let us know if you have any other questions!

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    There’s actually a spec for CSV format that suggests how to escape values that include quotes in CSV:
    https://datatracker.ietf.org/doc/html/rfc4180

    Why can’t this be used in those custom fields?

    Thanks.

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hello @alvarogois,

    Thanks for sharing that page — I passed it to our developers for an evaluation; I honestly can’t answer your question in technical details, so I asked our tech team to provide more insights if possible.

    We’ll circle back once we have something to share. Let me know if there’s anything else we can do to help meanwhile!

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hey there, @alvarogois,

    Upon talking to our developers, we have created a featured request about that!

    Thanks for reporting us and for helping us improve our product!

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Hi Stef,

    Thanks.

    I’m still having issues with custom fields and I can’t find the culprit.

    So, I have this custom field Course. It wasn’t being populated through the API using the Select format, as I mentioned before (I did test it without commas in the course names, to no avail).

    Now I deleted it and created the same Course field but as a Text field. It still isn’t being populated through the API. Other fields are. And I’m using the remote form to send the data also to a Google Sheet and all the fields get through.

    How can I debug this? I’m out of options here.

    Thanks.

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Can it have something to do with an error thrown by the JCRM API Connector in the source site? I mean, other fields are being passed but…

    The message in the logs is this:

    [05-Aug-2022 16:48:50 UTC] PHP Notice: Undefined variable: tag in /home/*****/public_html/wordpress/wp-content/plugins/jetpackcrm-ext-api-connector/includes/class-zerobscrm-apiconnector.php on line 467

    Thanks.

    Hi Álvaro,

    Can you provide more information on how you are passing this data? From what I understand from your previous messages, I thought you were importing a .CSV file. May I know how are you trying to populate the data in CRM?

    Also, it seems like you have a paid extension, it would be best to contact us by submitting a ticket here:

    https://kb.jetpackcrm.com/crm-support/

    This way, you’ll get priority support. Please reference this forum thread if you did create a support ticket. Thank you!

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Hi @aicee11

    I’ve never said I was importing a .CSV file, I was referring to custom fields being saved in CSV format.

    The issue was with the fields’ CSV format. Custom fields is a core feature, that’s why I asked here in the first place, in the hope JCRM core had already corrected this issue.

    Thanks.

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hey @alvarogois,

    I’ve never said I was importing a .CSV file, I was referring to custom fields being saved in CSV format.

    Thanks for clarifying that! That’s noted here now 🙂

    Now I deleted it and created the same Course field but as a Text field. It still isn’t being populated through the API. Other fields are. And I’m using the remote form to send the data also to a Google Sheet and all the fields get through.

    Can it have something to do with an error thrown by the JCRM API Connector in the source site? I mean, other fields are being passed but…

    This is a good input to lead and can help us untangle the problem.

    As Aicee said, since it seems like you have a paid subscription, you’re very welcome to reach out via email, so we can also be able to share sensitive information we cannot disclose in a public forum.

    Any questions, we’re here (and on email!) 🙂

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Hi Stef,

    I’ve opened a new ticket regarding the issue with the custom fields and API.

    Look forward to see the changes in the custom fields CSV format.

    Thanks.

    Jay

    (@bluejay77)

    Hi @alvarogois,

    We have received your ticket, and we’ll reply to you via email 🙂 Thanks!

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Custom fields with commas’ is closed to new replies.