Orphan Broadcasts

Daniel Marrujo shared this question 14 months ago
Answered

Hello team,


We had an issue where if a user that owns a broadcast leaves the company (and deleted from Yellowfin/Smart Reporting) then the broadcast will no longer run.


A quick fix for this is to simple edit the broadcast with another user and save it back, this will overwrite the ownership of the broadcast and works again normally, however this could create a Gap until this is solved manually.


In previous releases (8.0) you help us to include a functionality that wont allow to delete the users if they own private reports (to avoid orphan private reports), for this you will need to delete the user manually from the admin console and it will ask you who will be the new owner...., however broadcast were not included on this migration.


Could you please confirm this? This could be considered as a defect.

Comments (6)

photo
1

Hi Daniel,

Thanks for reaching out to support with your question. I did a quick test in 9.2.2 and it looks like this is working - if I deleted a user with a private report that had broadcasts scheduled, the report and broadcast owner were migrated -


79935c5a1d56b4a0a268e5cc2b624458

2d884630f713541d4e27bb2a8cc2eb37

Schedule manager showed "Last Run" updated at the scheduled interval after the change in ownership.

So it looks like these broadcasts are no longer orphaned after user deletion in newer versions. Is an upgrade a possibility in this case? Maybe there is something I'm missing in my testing?


Thanks,

Eric

photo
1

But this is clearly not working in 8.x versions. Only report ownership transfer is working not broadcast.


This will result in broadcast failures and can impact system performance which we have already experienced for multiple customers.


Can you please raise a DEFECT for this issue as broadcast ownership change is not happening on 8.x.


Kind Regards,

Asif Bhat

photo
1

Hi Asif,

I tested in Smart reporting 8.0.6

58f04849f6d0e2183cc21c1bedee51f7-Made private report and broadcast


1344247741cbe617aaca6d1f651118b6

-deleted user, migrated content -

cd947933cc087a6ef2478268dbc1ffa5


-broadcast ownership was transferred as expected -


510ddd24d5998458554a94afad0e99e5

Let me know if I'm missing anything here.

Thanks,

Eric

photo
1

What if the broadcast is PUBLIC ?

Will it transfer the ownership for public broadcasts ?

photo
1

Hi Asif,

Still working for me,

-created public report and broadcast as Bob

400440606b2b0ae18d384de73cc69a70b8a03699298e3ff73bb1a6c951183a13

Deleted bob using migrate content option -


e1a71904afc6b97eab5acac4f447f005

Broadcast showed siadmin ownership -

0a48af84a973afc39c9b49608f63ea75

Let me know if you need anything else.


Thanks,

Eric

photo
photo
1

HI Daniel,

Hope things are good on your end. Just wanted to check in to see if you had a chance to review my reply at this time?

Thanks,

Eric

photo
1

Thanks, are there any plans to migrate this functions to 8.x versions?

photo
1

Hi Daniel,

I just checked in a Yellowfin 8.0.6 build and the functionality works the same as 9.2 - my steps:

1. Create test "old user"

2. Make private report with only old user access, and create broadcast to system admin as old user

3. broadcast runs on schedule, but fails, "no access" (expected)

1678e4f8da7b27206556499312ac6d3a

4. login as admin, delete old user from admin console

5. choose option to migrate content to administrator, receive confirmation

ef515b1ec154c12cae3d079fa7ff8842

6. observe old user private report is accessible to system admin and broadcast to system to admin is running & allowing report access


d8aae26ed29909177ec0016470755eab

What version of 8.0 are you experiencing this on? It may be as simple as an upgrade to 8.0.6 here? Or perhaps there's something else I'm missing here?


Thanks,

Eric

photo
1

Hi Daniel,

Hope things are good on your end, just wanted to check in to see if you had a chance to review my reply at this time?

Thanks,

Eric

photo
1

Hi Daniel,

I'm going to go ahead and mark this ticket as Answered due to inactivity at this time. Feel welcome to re-open with a reply if you'd like to re-visit this issue sometime in the future.

Thanks,

Eric