Results 1 to 4 of 4
-
04-16-2010, 11:51 AM #1WEC Guest
Piping issues - Spaces in attribute names
When piping an attribute into the body of an invitation, it does not appear to work for any attribute that has a space in the name, such as "Site Name". Something about the piping does not like the white space, so an obvious fix seems to be to change the attribute name to something like "SiteName" or "Site_Name", however it appears you are unable to edit attributes once they are created.
So my question is, other than created a new attribute and copying the old data to the new attribute, is there any way to resolve this? I hope that is clear enough!
Thanks
-
04-16-2010, 12:00 PM #2
Administrator
- Join Date
- Mar 2007
- Posts
- 385
What version of the product are you using? I ask because the behavior your describe is a bug. When using a pipe that contains a space Checkbox should automatically replace the space with an underscore.
You are correct, there is no way to change a custom user field's name in the products UI. This is primarily because of the complexity of updating existing pipes which reference the field. That being said it is possible to change the name directly in the database. The following SQL will update the name.
--Begin
UPDATE [ckbx_CustomUserField]
SET [CustomUserFieldName] = 'New_Name'
WHERE [CustomUserFieldName] = 'Current Name'
--End
for example
--Begin
UPDATE [ckbx_CustomUserField]
SET [CustomUserFieldName] = 'First_Name'
WHERE [CustomUserFieldName] = 'First Name'
--End
-
04-16-2010, 12:05 PM #3WEC Guest
I am using Version 4.6.4.7.
I have a field "Site Name". When It is piped into the body of the invitation, it shows up as @@Site_Name but it is null when then invitation is actually received (and the Site Name does have data associated with it).
Thank you for your fast reply by the way!
-
07-01-2010, 01:08 PM #4
Administrator
- Join Date
- Mar 2007
- Location
- Prezza Technologies
- Posts
- 225
Hello,
This is just to update those following this thread that we've looked into the issue further and it looks like the issue occurs when an invitation is first sent. Piping appears to be correct for reminders and resends.
A fix for this issue will be in Checkbox 4.7, which we expect to release in early August.


LinkBack URL
About LinkBacks
Reply With Quote