• Replies 3 replies
  • Subscribers 336 subscribers
  • Views 97 views
  • Users 0 members are here
Related

Error opening plans screen -

Former Member
Former Member $organization

Hi,

We are getting an error when we try to open one constituent's plan screen. First an empty Information screen pops up. I click "OK". Then an Error screen pops up  saying "Last Error: Invalid DataWindow row/column specified at line 10 in function uf_load_security_rights of object uo_panel_constituent_single."

I have searched for uf_load_security_rights and uo_panel_constituent_single in SSMS as well as this website. Nothing has come up.

I modified the code from Tessitura’s [UP_FIND_INVALID_CHARACTERS] stored procedure to use on the steps in this plan to see if her steps have any funky characters. Nothing was returned.

Has anyone else seen this? What did you do to resolve it?  Or does anyone have any suggestions on what to try next?

Much thanks,
Debbie

Parents
  • Former Member
    Former Member $organization

    Ok. I solved my own problem. I am posting what I did in case it will help someone in the future. I did all this work via SSMS, not through Tessitura.

    This plan had 171 steps.

    I created a plan on my own record and started moving steps (grouped by step_type and then by YEAR(step_dt) - to create small enough groups) to my plan. Then I tested to see if the plan would open or not.  When my plan had 16 steps and would not open, I was finally able to get an error message that was helpful - "hexadecimal value 0x12 is an invalid character". So, I searched my steps for 0X12. I found it and replaced it.  This solved the problem and the plans open just fine now.

    Code to find and change the invisible character:
    SELECT plan_no, step_no, notes
    FROM dbo.T_STEP
    WHERE notes LIKE '%' + CHAR(0x12) +'%'

    --UPDATE dbo.T_STEP
    --SET notes = REPLACE(notes, CHAR(0x12), '')
    --WHERE notes like '%' + CHAR(0x12) +'%'

    Thanks,
    Debbie

Reply
  • Former Member
    Former Member $organization

    Ok. I solved my own problem. I am posting what I did in case it will help someone in the future. I did all this work via SSMS, not through Tessitura.

    This plan had 171 steps.

    I created a plan on my own record and started moving steps (grouped by step_type and then by YEAR(step_dt) - to create small enough groups) to my plan. Then I tested to see if the plan would open or not.  When my plan had 16 steps and would not open, I was finally able to get an error message that was helpful - "hexadecimal value 0x12 is an invalid character". So, I searched my steps for 0X12. I found it and replaced it.  This solved the problem and the plans open just fine now.

    Code to find and change the invisible character:
    SELECT plan_no, step_no, notes
    FROM dbo.T_STEP
    WHERE notes LIKE '%' + CHAR(0x12) +'%'

    --UPDATE dbo.T_STEP
    --SET notes = REPLACE(notes, CHAR(0x12), '')
    --WHERE notes like '%' + CHAR(0x12) +'%'

    Thanks,
    Debbie

Children