I'm interested in the use case for this and the problem/requirement that you're attempting to solve.
Hi Chul,
The full picture is that we are engaged in a clean up of a our metadata pre-implementation and need to clear out data from specific intersections. The built in functionality does it by Cube, Entity, Scenario, and Time. We need to be able to clear specific accounts for example.
The clearing itself will likely be straightforward, using data buffers built up from parameters selected in the Dashboard. The not straightforward issue is the presentation of the data to be cleared and then the intersections after the clear. This report is a pure validation report but we need it to display all dimensions just as the System > Tools > Data Base > Application Database > Tools > Data Records does.
I have yet to find a good and easy approach to present all the data without using this tool. This tool is also only accessible by admins. We want to reduce the amount of admins and instead attribute roles specifically to analysts and developers in a more precise way.
If you or anyone has a good way to visualize data using parameters, that allows interaction with dimension (metadata) hierarchies, and allows for non-Administrator access I would really appreciate it.
You can create a data adaptor with Method Query and use method type "Data Units" and then pass parameters to it Create a dashboard with Grid View which use this data adaptor and convert parameters into combo boxes and apply that to Grid View component in dashboard
Whenever users will select the parameters, it will bring data from data records table for those filters and dashboard can be applied with required security
Syntax
{Cube}{Entity}{Parent}{Cons}{Scenario}{Time}{View}{True}{Empty String or Filter Expression}
Example
{Golfstream}{|!prm_Entity!|}{}{|!prm_Cons!|}{|!prm_Scenario!|}{|!prm_Time!|}{|!prm_View!|}{True}{Account = 'Cash' And Flow = 'None'}
Hi VishalPai,
This method does show all metadata but I am struggling to get it to work with expansion functions. For example E#Child1 works but E#Parent1.Base fails to show anything.
