Custom Fields Tag and Name columns

[bryananaya]

Is it possible to have the name and tag different for custom fields? I don't currently see a way to do this. Can I request that this feature be added?
Use Case:
I want to use the name of the custom field as a question in my UI pulled in from Mumara API.
Then post back into that field via the tag, like how it is today.
I am trying to avoid having to map a tag to a long string and just use the API for all the data.

If I go into the custom_fields table and change the name manually, will that cause any issues?

 

[wasif]

@bryananaya, my apology for the delay in response, as this thread wasn't appearing in the latest threads. You can also use subscribe ID for this purpose. Moreover, I would need to accept that I didn't get your question. Can you rephrase or explain a little more?

 

[bryananaya]

No problems.

Basically the question is specific to custom fields. Can the tag and name be different?

Example. If I have a custom field of "Newsletter Preferences" it currently will insert that into the name field and newsletter_preferences into the tag field of the custom_fields table in the db. What I would like is something like "Newsletters User has subscribed to" (not real, just an example) but I don't want to have to target newsletters_user_has_subscribed_to as the tag in the API. I would like to have something like newsletter_subs for the API/tag.

I realize this is an edge case and very specific, so if I went into the db and changed either the tag or name in the custom_fields table manually, would that cause a problem?

 

[mohammad]

@bryananaya If you utilize a custom field in the broadcast and subsequently modify the corresponding custom field tag in the database, that tag will not work anymore.