• Replies 3 replies
  • Subscribers 337 subscribers
  • Views 21 views
  • Users 0 members are here
Related

InfoMaker data issue

Former Member
Former Member $organization

I am having an issue with a custom report field that is returning a 0 instead of the amount returned by the SQL Server stored procedure when it is executed on the server.  All of the fields lineup in the report with the columns in SQL, and the data type is correct in the report,  but we are getting an erroneous value in this one field??  See the example below:

 

SQL 2012
solicitor cur_fy_goal
jlandin  50000
   
Report 2012
solicitor cur_fy_goal
jlandin 0

  • $organization

    A few other basic things to check, but are you pointed at the correct DB in Infomaker?

     

    You can also try running a trace to see if there is a difference between how you are executing it in SSMS vs how Infomaker is providing parameter values.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of James Fairfield
    Sent: Wednesday, June 15, 2011 9:20 AM
    To: Ryan Creps
    Subject: [Tessitura Technical Forum] InfoMaker data issue

     

    I am having an issue with a custom report field that is returning a 0 instead of the amount returned by the SQL Server stored procedure when it is executed on the server.  All of the fields lineup in the report with the columns in SQL, and the data type is correct in the report,  but we are getting an erroneous value in this one field??  See the example below:

     

    SQL

    2012

    solicitor

    cur_fy_goal

    jlandin

    50000

     

     

    Report

    2012

    solicitor

    cur_fy_goal

    jlandin

    0




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • Former Member
    Former Member $organization in reply to Ryan Creps (Past Staff Member)

    Ryan:

    Thank you.  I ran a trace, and the parameters being passed are the same.  A friend of ours installed our SP and created a report, and the problem does not show up on his system. ???

     

    James

  • Former Member
    Former Member $organization
    Hi James
    One approach I've found useful with mysterious IM problems is simply to start again - ie open a new report, link it to the proc, and do a basic auto table layout, and see what you get. If you get the right data, then you can throw away your old report without ever spending the time fretting about what was wrong with it, and you've only lost the time needed to re-create the report (it's always faster the second time) - and you avoid the risk of going mad and screaming abuse at the screen, which is not good for your reputation, even though other infomaker users will understand.
    Ken McSwain :: sent from the Blackberry
     
    From: James Fairfield [mailto:bounce-jamesfairfiled8203@tessituranetwork.com]
    Sent: Thursday, June 16, 2011 03:20 AM
    To: Ken McSwain
    Subject: RE: [Tessitura Technical Forum] InfoMaker data issue
     

    Ryan:

    Thank you.  I ran a trace, and the parameters being passed are the same.  A friend of ours installed our SP and created a report, and the problem does not show up on his system. ???

     

    James

    From: Ryan Creps <bounce-ryancreps9649@tessituranetwork.com>
    Sent: 6/15/2011 9:35:07 AM

    A few other basic things to check, but are you pointed at the correct DB in Infomaker?

     

    You can also try running a trace to see if there is a difference between how you are executing it in SSMS vs how Infomaker is providing parameter values.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of James Fairfield
    Sent: Wednesday, June 15, 2011 9:20 AM
    To: Ryan Creps
    Subject: [Tessitura Technical Forum] InfoMaker data issue

     

    I am having an issue with a custom report field that is returning a 0 instead of the amount returned by the SQL Server stored procedure when it is executed on the server.  All of the fields lineup in the report with the columns in SQL, and the data type is correct in the report,  but we are getting an erroneous value in this one field??  See the example below:

     

    SQL

    2012

    solicitor

    cur_fy_goal

    jlandin

    50000

     

     

    Report

    2012

    solicitor

    cur_fy_goal

    jlandin

    0




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
    Hear Australia's Stradivarius violin in the Baroque Virtuosi tour (3-14 July).
    Explore the ACO&#x02019;s 2011 season at aco.com.au/season2011

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.