Use of "additional user defined data" in constituent imports

Part of the preparations for constituent imports files are 10 local use fields for "additional user defined data." I understand that  these fields are used to import custom data into custom order fields. I would like to hear from folks about what kind of data they have used these fields in their own imports. 

Thanks in advance.

Parents
  • For our ticketing imports, we've used it to match up third-party source codes with Tessitura source codes using the LP_ORDER_IMPORT procedure and a local source code match-up table. We used another local use field to import email preferences from the third-party ticketing platform... Basically you can use these fields to import any additional information you want to capture from the original database that isn't a default option in the import set. You can configure that information to drop it into various fields by adding custom code to the LP_XXXX_IMPORT procedures. 

Reply
  • For our ticketing imports, we've used it to match up third-party source codes with Tessitura source codes using the LP_ORDER_IMPORT procedure and a local source code match-up table. We used another local use field to import email preferences from the third-party ticketing platform... Basically you can use these fields to import any additional information you want to capture from the original database that isn't a default option in the import set. You can configure that information to drop it into various fields by adding custom code to the LP_XXXX_IMPORT procedures. 

Children
No Data