Hi Patrick, you are faster in understanding the details than I could look them up :-)
Yes, again I should have noticed, but I lack the daily sync practice... Every property that can occur multiple times, i.e. maps to a series of side-by-side fields or array fields, needs the <position> tag to specify how the multiple instances are to be filled into fields. This has nothing to do with "groupfield" directly, but of course "groupfield" usually does not make sense for non recurring properties. On 29.04.2014, at 17:48, Patrick Ohly <patrick.o...@intel.com> wrote: > Looking further at aPropP->nameExts it seems that this what relates to > <position> in the profile config. Exactly. (the reason why it is called "nameExts" internally is because in the early days, the primary usage was to direct TELs into one of multiple TEL fields based on WORK, HOME, FAX, so these worked as "field name extensions". Like having fields TEL_WORK and TEL_HOME, and two <position>s that routed incoming TELs according to TYPE using the "has" and "hasnot" attributes) > I did not have that for my X-ABLabel. > Adding it seems to fix the problem. So it seems that "groupfield" can > only be used reliably with a <property> which has a <position>, correct? Correct, see above. Best Regards, Lukas
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ os-libsynthesis mailing list os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
