• Replies 7 replies
  • Subscribers 338 subscribers
  • Views 83 views
  • Users 0 members are here
Related

Merging anomaly

Debbie Harland (Past Member)
$organization

Hi All,

On our Merge screen, we have two constituents in the Keep ID's column and one in the Delete ID's column all of which are totally unrelated to each other.

I can't remove them. I've tried unscheduling, but it doesn't help. 

I've tried adding in another Constituent ID to match the Delete ID to one which is a genuine merge for it, but I get a message saying the Constituent is involved in another merge and should be unscheduled first.

Don't know what else to try. Has anyone else seen this? Is it a thing that has a solution?

Thanks, Debbie

 

  • $organization in reply to Ruth Harris

    Hi Ruth,

    Yes please to the fix. These records have been sitting there for ages and they upset my sense of tidyness!

    Thanks very much. Debbie

  • $organization

    We're on 12.5.1 and have this problem fairly regularly too. It was supposed to have been fixed by a hot fix and RAMP can't recreate it. However, I agree with Ruth's analysis on what causes the issue. I'm always (intentionally) typing in keep and delete ids that aren't the recommended ones.

  • $organization

    Hi Debbie

     

    Yes we’ve seen this, and have added a process to tidy up these ‘orphans’ each night.  I can send it to you if you wish?

     

    I think it happens when typing in a keep id, which then prompts a suggested delete id, and then I type in an alternative delete id.  The scheduled merge shows only the keep id with no corresponding delete id.  I then do it again and it works.

     

    Thanks

    Ruth

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Debbie Harland
    Sent: 06 September 2016 15:47
    To: Ruth Harris <ruth.harris@rsc.org.uk>
    Subject: [Tessitura Technical Forum] Merging anomaly

     

    Hi All,

    On our Merge screen, we have two constituents in the Keep ID's column and one in the Delete ID's column all of which are totally unrelated to each other.

    I can't remove them. I've tried unscheduling, but it doesn't help. 

    I've tried adding in another Constituent ID to match the Delete ID to one which is a genuine merge for it, but I get a message saying the Constituent is involved in another merge and should be unscheduled first.

    Don't know what else to try. Has anyone else seen this? Is it a thing that has a solution?

    Thanks, Debbie

     




    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!

  • $organization

    I would love that fix too if you’re will to share.  It makes me a bit crazy to see those oddballs floating around.

     

    Michelle Usadel
    Tessitura Application Specialist | The Phoenix Symphony | Tel.  602-452-0441 | Fax. 602-253-1772
    www.phoenixsymphony.org | 1 N. 1st Street, Ste. 200, Phoenix, AZ 85004


     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Debbie Harland
    Sent: Tuesday, September 6, 2016 8:14 AM
    To: Michelle Usadel <musadel@phoenixsymphony.org>
    Subject: RE: [Tessitura Technical Forum] Merging anomaly

     

    Hi Ruth,

    Yes please to the fix. These records have been sitting there for ages and they upset my sense of tidyness!

    Thanks very much. Debbie

    From: Ruth Harris <bounce-ruthharris2141@tessituranetwork.com>
    Sent: 9/6/2016 2:59:10 PM

    Hi Debbie

     

    Yes we’ve seen this, and have added a process to tidy up these ‘orphans’ each night.  I can send it to you if you wish?

     

    I think it happens when typing in a keep id, which then prompts a suggested delete id, and then I type in an alternative delete id.  The scheduled merge shows only the keep id with no corresponding delete id.  I then do it again and it works.

     

    Thanks

    Ruth

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Debbie Harland
    Sent: 06 September 2016 15:47
    To: Ruth Harris <ruth.harris@rsc.org.uk>
    Subject: [Tessitura Technical Forum] Merging anomaly

     

    Hi All,

    On our Merge screen, we have two constituents in the Keep ID's column and one in the Delete ID's column all of which are totally unrelated to each other.

    I can't remove them. I've tried unscheduling, but it doesn't help. 

    I've tried adding in another Constituent ID to match the Delete ID to one which is a genuine merge for it, but I get a message saying the Constituent is involved in another merge and should be unscheduled first.

    Don't know what else to try. Has anyone else seen this? Is it a thing that has a solution?

    Thanks, Debbie

     




    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!
  • $organization

    We’ve created a daily job in sql to run this code –

     

    USE IMPRESARIO

     

    DELETE k FROM T_POTENTIAL_DUPS k

    LEFT JOIN T_POTENTIAL_DUPS d ON d.criterion = k.criterion AND d.status = 'D' AND k.status='K'

    WHERE

    k.status='K'

    AND d.criterion IS NULL

     

    Thanks

    Ruth

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Michelle Usadel
    Sent: 06 September 2016 16:29
    To: Ruth Harris <ruth.harris@rsc.org.uk>
    Subject: RE: [Tessitura Technical Forum] Merging anomaly

     

    I would love that fix too if you’re will to share.  It makes me a bit crazy to see those oddballs floating around.

     

    Michelle Usadel
    Tessitura Application Specialist | The Phoenix Symphony | Tel.  602-452-0441 | Fax. 602-253-1772
    www.phoenixsymphony.org | 1 N. 1st Street, Ste. 200, Phoenix, AZ 85004


     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Debbie Harland
    Sent: Tuesday, September 6, 2016 8:14 AM
    To: Michelle Usadel <    musadel@phoenixsymphony.org>
    Subject: RE: [Tessitura Technical Forum] Merging anomaly

     

    Hi Ruth,

    Yes please to the fix. These records have been sitting there for ages and they upset my sense of tidyness!

    Thanks very much. Debbie

    From: Ruth Harris <bounce-ruthharris2141@tessituranetwork.com>
    Sent: 9/6/2016 2:59:10 PM

    Hi Debbie

     

    Yes we’ve seen this, and have added a process to tidy up these ‘orphans’ each night.  I can send it to you if you wish?

     

    I think it happens when typing in a keep id, which then prompts a suggested delete id, and then I type in an alternative delete id.  The scheduled merge shows only the keep id with no corresponding delete id.  I then do it again and it works.

     

    Thanks

    Ruth

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Debbie Harland
    Sent: 06 September 2016 15:47
    To: Ruth Harris <    ruth.harris@rsc.org.uk>
    Subject: [Tessitura Technical Forum] Merging anomaly

     

    Hi All,

    On our Merge screen, we have two constituents in the Keep ID's column and one in the Delete ID's column all of which are totally unrelated to each other.

    I can't remove them. I've tried unscheduling, but it doesn't help. 

    I've tried adding in another Constituent ID to match the Delete ID to one which is a genuine merge for it, but I get a message saying the Constituent is involved in another merge and should be unscheduled first.

    Don't know what else to try. Has anyone else seen this? Is it a thing that has a solution?

    Thanks, Debbie

     




    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!

     
     
     
     
     
     
     
     
     




    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!

  • $organization in reply to Michelle Kosmatka

    I just wanted to let everyone on this thread know that this is a known issue in the current version of Tessitura and we do expect it to be fixed in V14.   If you have any questions about this, please feel free to open a Support ticket and we would be happy to discuss.

    Dale