Custom Screen Not Saving Updates

I'm sure this is a stupidly simple thing to fix, but I'm feeling a bit stumped at the moment.

I've just created a custom tab in Tessitura using a custom table connected to an InfoMaker object.

The custom tab works in so far as I can delete or add entries to it. However, once an entry is added, if I try to change the data in a field, or delete the data in the field, it will appear to change, but if I move to another tab or click Save, nothing happens and once I come back to the tab, the old bits will be there.

Meanwhile, I can add new values to blank fields with no trouble at all. It's just modifying existing fields that's giving me grief.

Hints, anyone?

  • Do you have an update table defined in TR_CUSTOM_TAB?

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Matthew Hodge
    Sent: Monday, September 13, 2010 10:56 PM
    To: Ryan Creps
    Subject: [Tessitura Shared Reports Forum] Custom Screen Not Saving Updates

     

    I'm sure this is a stupidly simple thing to fix, but I'm feeling a bit stumped at the moment.

    I've just created a custom tab in Tessitura using a custom table connected to an InfoMaker object.

    The custom tab works in so far as I can delete or add entries to it. However, once an entry is added, if I try to change the data in a field, or delete the data in the field, it will appear to change, but if I move to another tab or click Save, nothing happens and once I come back to the tab, the old bits will be there.

    Meanwhile, I can add new values to blank fields with no trouble at all. It's just modifying existing fields that's giving me grief.

    Hints, anyone?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!

  •  

    Yes, I do have the update table specified. That’s why I’m a bit mystified. And adding things to the table works fine. It’s deleting or modifying existing fields that’s the problem.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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 Matthew Hodge

    I just hit this recently

    1. Do you have the right security checked in the Security Module

    2. Are you getting any errors -- try running a trace

    3. Are you using the NOEDIT tag somewhere -- sometimes that can throw you off.

    4. Are your columns on the report in the same order as your sql statement. 

     

  • Lucky last – thanks for that, Fran! It was the columns out of order on the SELECT statement. I fixed that up and it’s all working fine.

  • Actually, I spoke too soon. But at least now I know exactly what the problem is.

    What I'm having trouble with is saving changes to a custom screen, if I delete the contents of a field.

    It's a number field (int to be specific), so to give an example, if I was to change the number from 100 to 99, it'll save no problems. If the field is blank and I add a new number, then that's fine too.

    But if I backspace out the 100 and move to another tab, I won't be prompted to save and when I come back to the custom tab the 100 is back.

    Has anyone seen this one before? I checked the underlying table to see if it accepts nulls and it does, so I'm not sure why I'm having this issue.

  • Daft question, but is the number field in question nullable?

  • No such thing as a daft question here . . . yes, I double-checked and the field is able to accept nulls.