• Replies 8 replies
  • Subscribers 337 subscribers
  • Views 43 views
  • Users 0 members are here
Related

Custom Tab crashing

Darrin Katz
$organization

Hi everyone,

 

I've been struggling all day trying to modify the Volunteer custom tab that I downloaded from Footprints, so any help you can offer would be very much appreciated.

 

After making some changes to the data window, the custom tab stops using the "default look and feel". Further, when I try to interact with the tab, such as by adding a row, Tessitura throws an error regarding a completely unrelated datawindow, for example, "w_donor_maint" and crashes out.

 

I can reproduce this error by starting with the Volunteer tab downloaded from Footprints, which "out of the box" works just fine. After deleting the "vol_date" column in the table definition in the database and going to Design -> Data Source in Infomaker to update the datawindow it becomes corrupted somehow. From then on I experience the crash as described above when I try to add a row via Tessitura.

 

Please see the attached screenshot.

My goal is to customize the canned custom report with our specific business needs, so I need to be able to remove some of the existing columns, add new columns, and so on.

 

I am extremely grateful for any assistance you can provide.

 

Regards,

Darrin

  • $organization

    HI Darrin,

    Good day.

    I downlaoded the sample code, checked the infomaker screen, but I haven't installed them.

    but I believe that you need to delete the text control too.

    "cal_vol_date"  is a funcation create by Tessitura only, it should show a calendar when you click it. (if you put "cal_" in front of date field, then text control becomes a function.)

    since vol_date was missing, then this function couldn't link to anywhere, then you saw the error message.

    have fun.

    thank you for your time.

    Ben

  • $organization

    Hi Darrin,

    finally I installed the custom screen, and did some test.

    1, I believe you already deleted cal_vol_date text control.

    2, if it was about cal_vol_date, the error message is different.

    the objectevent is "clicked". 

    so, the most possibly what happened was, Tessitura was not totally closed and started again.

    Any customer reports or customer screens if they are modified by infomaker, Tessitura needs to be 100% closed, then restart it. 

     

    Thank you for your time.

    Ben

  • $organization
    Hi Ben,
     
    I really appreciate you taking the time to look into this.
     
    I've attached a screenshot of my datawindow in which you can see that I am not using the cal_vol_date control at all. It does not appear on my list of controls. Please note that from within Infomaker I am able to Retrieve Rows without any problems.
     
     
    Each time I make any changes to the datawindow, I always close Tessitura and open it up again. Each time I close 100% out of Tessitura and open it up again, I encounter this problem without fail.
     
    Finally, the Objectevent that is causing the error is "wf_add_record" (please see the screenshot from the first post in this thread) and occurs when I use Tessitura's Add button at the bottom of the custom tab screen, not when I interact with the elements in the custom tab itself.
     
    Thanks again for all of your help,
    Darrin
  • $organization in reply to Darrin Katz

    Hi Ben,

    My apologies for not correctly attaching my screenshot in the last email. This is the image I was referring to:

     

     

    Thanks again,

    Darrin

  • $organization in reply to Darrin Katz

    Hi Darrin,

    I have compared your xml sub-screen with mine and original screen.

    I found the customer_no and id_key on your screen are "Literal text", on myscreen or on original screen is "Computed field or Infomaker expression reference".

    I have no idea what happened on these two fields. Possibly you have to modify the data source again.

    According to the docs from google, the "Literal text" will not response to a function.

    have fun.

    thank you for your time.

    Ben

  • $organization in reply to Ben Gu

    Hi Darrin,

    here is my screen.

    thank you for your time.

    Ben

     

  • $organization
    Hi Ben,
     
    Thank you so much for your help! By simply deleting the children of the customer_no and id_key elements in the XML, Tessitura was able to read the datawindow properly.
     
    I really appreciate the time you've taken to help me out with this, as your solution has completely solved my problem and I was able to implement the custom tab I was working on.
     
    Regards,
    Darrin
  • $organization
    Hi Ben,
     
    Thank you so much for your help! By simply deleting the children of the customer_no and id_key elements in the XML, Tessitura was able to read the datawindow properly.
     
    I really appreciate the time you've taken to help me out with this, as your solution has completely solved my problem and I was able to implement the custom tab I was working on.
     
    Regards,
    Darrin