If my form has 15 fields in it, rather than passing all 15
fields to the
target template, could I...
- create a struct variable (e.g. UserProfile),
- name each form field as a variable under the struct
(e.g.,
UserProfile.FirstName, UserProfile.LastName)
- still be able to use the
Was trying to use the WDDX method to pass a long form set. Would only pass a random 10
fields. Found by searching on this forum that this is a known MX bug. Workaround is to
Duplicate the form first, then serialize with WDDX. Worked fine sending the total form
as structure via wddx IF did the
Look into using wddx and the cfwddx tag.
In short you would create a structure, use the cfwddx to convert it to wddx,
use a hidden variable to pass the wddx packet to the receiving page and then
use cfwddx to convert the packet back to a structure.
Its exactly what wddx and cfwddx is designed
Look into using wddx and the cfwddx tag.
In short you would create a structure, use the cfwddx to convert it to
wddx,
use a hidden variable to pass the wddx packet to the receiving page and
then
use cfwddx to convert the packet back to a structure.
Its exactly what wddx and cfwddx is
If my form has 15 fields in it, rather than passing all 15 fields to the
target template, could I...
- create a struct variable (e.g. UserProfile),
- name each form field as a variable under the struct (e.g.,
UserProfile.FirstName, UserProfile.LastName)
- still be able to use the struct
5 matches
Mail list logo