Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communication Merge Fields Only Accept Text #802

Closed
BelAirIT opened this issue Jan 26, 2015 · 3 comments
Closed

Communication Merge Fields Only Accept Text #802

BelAirIT opened this issue Jan 26, 2015 · 3 comments

Comments

@BelAirIT
Copy link

I have a few custom Person Attributes and am trying to use them in a communication. Only the attributes that are stored as text show up as available, though. I have a day of the week and time attribute that do not show up in the merge field list.

@azturner
Copy link
Contributor

@BelAirIT , I haven't been able to reproduce this based on just the field type (i.e. only text attributes showing up). I did notice that if an attribute is secured in any way, the attribute won't appear in the list of available attributes, could this be the issue you are experiencing? If so, that will be fixed for next update and until then, you can still use the attribute by typing the lava syntax directly into the communication ( e.g. {{ Person | Attribute:'attributekey' }} ).

@BelAirIT
Copy link
Author

Thanks @azturner, that does appear to be the case. The Person Attributes that are secured don't show up in the list. But I also can't manually reference them as you suggested either. They simply do not populate the communicate like the unsecured ones do. Hopefully this will be resolved in the next update.

@azturner
Copy link
Contributor

@BelAirIT , Yep, you're right, does look like even the manually entered ones won't work due to the send process not having knowledge of who the current person is in order to determine security. We've updated this also to work in the v3.0 update.

azturner added a commit that referenced this issue Feb 23, 2015
…eated the communication when resolving merge fields so that secured attribute values can actually be included in a communication (Fixes #802).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants