Hello,
We've got a localized acknowledgement in T_FORMAT_INFO - it pulls data into an infomaker report.
The report is generated from inside an order (print acknowledgments pop/screen). one of the parameters that gets passed is mailing_dt and mailling_dt for some reason (when i don't explicitly specify this parameter anywhere picks 1/1/1900 -- where is this parameter set? How do I find this value for this particular confirmation? We did a trace and we see parameter is passing 1/1/1900 for each date value. Where is this defined and how do we change it? Also how do we add an infomaker parameter as part of the output - there is no parameter option under insert?
the second part is that the mailing_dt actually gets updated in the code based on some criteria -- and we've tested it through out pieces of the code in an effort to find if the changes stick through out. We know the value gets updated correctly because we added it to the end of the result set to see the actual updated value. However the confirmation seems to not see these updates? (as it returns the original parameter value). Why is that? How do we remedy this?
Thank you.
-Lisa
We assume that the mailing datatime is the current date/time when called from the Order Print window directly. This is why you see 1/1/1900 (which is a default if not provided). You can customize an order acknowledgement or confirmation to utilize a local procedure. From the order window, the only parameters that get passed is the format_id, order_no, and a report type ('O' in this case). You should make that assumption that if passed as null or '1/1/1900' that the current date/time should be used. In TP_ORDER_ACK, one of the assumptions that is made is if the type is 'O' then we set the @mailing_dt to GETDATE(). Feel free to look at this proc as a starting point for a local procedure, or as guidance for how things work.
Also, from the order print window, there is no way to add additional parameters or change the default behavior.
The Order Confirmation and Acknowledgement formats (Infomaker versions, not the HTML versions) do few things inside the client app to format the output that cannot be easily controlled from the report/datawindow itself.
Hope that gets you further in your journey!
--Ryan Creps
Thank you Ryan Creps (Past Staff Member) for the response.
Its interesting that only the three values you list are what are passed, when i trace the execute it seems the statement gets a lot of parameters with passed values -- and all the dates are set to '1/1/1900'. I am not looking to add parameters just figure out why changes in logic aren't sticking. The logic updates the date value but that is not what is returned to the informaker/letter.
What i mean is when I dived into the logic where if type = 'O' then the order date does get updated to getdate(). Only problem is that it is SQL is making the updates and saving those updates to the parameter values (i checked the final select). However, when the data gets passed back to the informaker file the changes are lost or not kept. The infomaker (or Tessitura) file seems to always return and print the original 1900 value without any changes.
That is why I had asked about data windows and infomaker. I was curious how update-able/customize-able any of the data windows really are. Thank you again. -Lisa
As Martin indicates below, the procedure execution is consistent, a set number of parameters is consistently passed for all order confirmations/acknowledgements, but with type 'O' only a few are utilized.
Hello Ryan, I understand what you are saying the issue is that the parameter is utilized and even updated in the sql however all changes that occur (Getdate()) aren't passed back to the infomaker/tessitura. The report generates a '1/1/1900' even after the sql changed the mailing_dt to getdate(). that is my confusion.