New Topic

Community Topic Idea Chart Builder

Deepak Chaganti

Yellowfin Support Team

Assigned

Category Chart Builder

Product Version 9.0

Displays detailed information when an action is rejected by YF because "still used".

Stefan Hall shared this idea ago

Idea Logged

As an administrator and view creator, it is very annoying when actions cannot be performed because something is still "in use". No one is helped by the general message box "not possible, still in use in (report / view / ..)" if the originator is not clearly identified.

Business case
This happens quite often when you have to clean up views or want to restructure something. YF itself doesn't always seem to have everything under control either and is mistaken about the message.

All in all, an annoying process when even for such simple questions as "In which report is the field used?" you can only clarify at database level. That should be easier, shouldn't it?

Report guessing takes time, a lot of time, and database access requires too much detailed knowledge and is unnecessarily dangerous.

;) Stefan

I like this idea 0

Replies (5)

Deepak Chaganti ●

Hi Stefan,

Thanks for reaching out.

I understood the first requirement (display name of the user who is editing the view/report). In YF 9.8.0.1, editing a view doesn't throw the name of the user but editing a report does provide the details of the user who is editing that particular report (please refer to the attached images). Could you please let me know if I am on the right track and looking for name of the user also on view edit dialogue box?

And coming to the second requirement, (finding the report in which a particular field is being used), Yes, we have to rely on db for the information:
SELECT ReportName FROM reportheader as h
WHERE ReportId in (
SELECT ReportId FROM reportfield f, reportfieldtemplate t
WHERE t.FieldTemplateId=f.FieldTemplateId
AND t.ColumnName='DEMOGRAPHIC');

May be another way(if db access to a non DBA is the main issue), then we could connect cofig db as a data source and then create a report that would fetch the required data.

Thanks,

Deepak

Files:

Reply URL

Stefan Hall ●

Hi Deepak,

it would not be a reasonable extension of your system that an administrator/view designer has this information generally available.

Is already a strange behavior at the UI that YF tells me something is used but keeps the details secret. The more reports and writers you have in the system, the worse this meaningless error message gets.

The workaround is ok, but definitely not a viable solution for a professional application.

;) Stefan

URL

Deepak Chaganti ●

Hi Stefan,

I have gone ahead and created request with the wider team to consider the implementation of the requirements:

1. Display the user/details who is editing a view (concurrent user name)

2. Details like 'Report names that are using a particular field' to be displayed in UI to admin user.

I will post the updates here in this idea.

Best Regards,

Deepak

Reply URL

Stefan Hall ●

Hi,
Even your support staff noticed this missing feature during the last call. He thought the current implementation was really bad.

I can understand, because if your car mechanic tells you that he can't do something because something is activated in the car, but doesn't tell you, then you are also speechless and helpless.

;) Stefan

Reply URL

Deepak Chaganti ●

Hi Stefan,

Thanks for sharing the response.

Could you please confirm the other ticket that also required this feature? I will add that ticket to the enhancement request previously made.

And I will also reference the other ticket and follow up with the product team.

Regards,

Deepak

Reply URL

Stefan Hall ●

Hi Deepak,

You misunderstood me. We had a live call with one of your support employees and he also had to get the information by looking at the DB. He said, “oh god” that's bad and yes, he was right in his assessment.
As customers and users, we don't want to go to DB level to get normal and complete error information.

Please ping your product management again and ask them how to find out where a certain field of a view is used. If the answer is “just look in the database itself”, you should have enough reasons to implement the idea.

;) Stefan

URL

Deepak Chaganti ●

Hi Stefan,

Thanks for letting me know.

I have conveyed this to the product team, and they will review this enhancement request in the future.

Regards,

Deepak

Reply URL