Hello, I'm tying to use the NCOA Proccessing utility/reort to create an export file.
I fill out all of the required fields, as well as some of the optional ones, but no matter what values I choose, Tessitura always gives me the following error...
"Retrieve argument 6 does not match expected type"
It's pretty vague, I thought maybe that refered to the 6th paremeter on the list (Include Address Types) but after playing around with various combinations, I don't think the "6" has anything to do with that.
Has anyone seen an error like this? Not sure what I should do to get this export to work correctly.
Porter Venn, San Francisco Opera.
Hi Porter
It normally means there's a mismatch of data types between how Parameter 6 (in this case) is defined in the Report Setup utility (a string) and what Infomaker expects the parameter to be (integer, string, datetime).
I have looked at the Infomaker object as it stands in the Tessitura Version 9 library and it looks as if the Include Address Types parameter is missing completely (open the Infomaker report, right click on the Column Specifications panel, select Stored Procedure, then click on Arguments).
Looks like this is the culprit. Parameter 6 in the Infomaker object (nIncludeList) is an integer while the Address Type parameter being passed is a string.
Might need to escalate this to Tessitura Help Desk.
Regards
David Joyce
Hi Porter,
Good day.
based on info from d_ncoa_process and info from [dbo].[AP_NCOA_PROCESS],
this is a bug.
execute dbo.AP_NCOA_PROCESS;1 @cAction = :cAction, @lNCOASession = :lNCOASession, @sExportFileName = :sExportFileName, @sImportFileName = :sImportFileName, @nLimitToCountry = :nLimitToCountry, @nIncludeList = :nIncludeList, @nExcludeList = :nExcludeList, @sIncludeConstituencySet = :sIncludeConstituencySet, @sExcludeConstituencySet = :sExcludeConstituencySet, @lBeginningCustomerNo = :lBeginningCustomerNo, @cAddressFormat = :cAddressFormat, @cTelephoneAppend = :cTelephoneAppend, @nPhoneType = :nPhoneType, @nPhoneTypeApp = :nPhoneTypeApp, @cRemoveUnconfirmedPhone = :cRemoveUnconfirmedPhone
ALTER PROCEDURE [dbo].[AP_NCOA_PROCESS] (@cAction char(1), -- E)xport, I)mport, P)rocess@lNCOASession int = 0,@sExportFilename varchar(255) = NULL,@sImportFilename varchar(255) = NULL,@nLimitToCountry int = 1,@sAddressType varchar(255) = NULL, -- RAP FP1340. Use null to include all address_types@nIncludeList int = 0,@nExcludeList int = 0,@sIncludeConstituencySet varchar(255) = NULL,@sExcludeConstituencySet varchar(255) = NULL,@lBeginningCustomerNo int = 1,@cAddressFormat char(1) = 'S',@cTelephoneAppend char(1) = 'Y',@nPhoneType int = 1,@nPhoneTypeApp int = 1,@cRemoveUnconfirmedPhone char(1) = 'N',@cDebug char(1) = 'N')
have fun
Ben
Thanks for the tips guys, yup it looks like a bug. I'm going to submit a TASK ticket.
Porter
Actually I'm not so sure. The address type parameter is multi-select so the procedure expects (and gets) a string, parsing as necessary. See my trace below.
I mention it because I used the report just the other week with pretty good results. I had left the addresstype as null but in testing I'm also having sucess with limiting to one or more address types--something I'll probably do for future runs. The price for the NCOA updates is certainly good anyway and I used a list to exclude higher donors as well as season subscribers.
execute dbo.AP_NCOA_PROCESS @cAction = 'E', @lNCOASession = NULL, @sExportFileName = 'test.txt', @sImportFileName = NULL, @nLimitToCountry = NULL, @sAddressType = '3,11', @nIncludeList = 34550, @nExcludeList = NULL, @sIncludeConstituencySet = NULL, @sExcludeConstituencySet = NULL, @lBeginningCustomerNo = 10, @cAddressFormat = 'S', @cTelephoneAppend = 'N', @nPhoneType = NULL, @nPhoneTypeApp = NULL, @cRemoveUnconfirmedPhone = NULL
You should submit a Task support for this. I believe there is a fix/patch for this specific error.
The fix David mentions is in the 9.0.0.2 post-release patch. If you can apply that, it should resolve the issue for you. Otherwise, as advised, please open a help ticket.
Thanks everyone for the help and suggestions.
I spoke with Rob Pedersen and he got me squared away.
We are still on 9.0.0.1, so we needed to do two things to make this work. First we updated the .PBD file to the latest version, and then second Rob sent me the updated version of the AP_NCOA_PROCESS stored procedure, this included a few bug fixes that we didn't have in 9.0.0.1.
Now everything works fine, We're still on 9.0.0.1 for the time being, but I guess you can say our NCOA functionality is 9.0.0.2.
Thanks everyone for your tips and help on this!