Pivot Grid (OLAP) avoid adding fields to inappropriate zones

4 posts, 0 answers
  1. Yohan
    Yohan avatar
    32 posts
    Member since:
    Jan 2014

    Posted 01 Jan 2014 Link to this post

    Pivot grid allows users to add any field to any zone type, but in OLAP connection it doesn't make sense because only measure fields give a meaningful data representation when added to aggregate zone and other dimension fields adding to column/row/filter zones. Configuration Panel Fields Context Menu is misleading because when clicked on any dimension it allows user to add any field to any zone as mentioned. how to avoid this. Disable  "move to aggregate fields" for dimension fields and enable only  "move to aggregate fields" for measures in Configuration Panel Fields Context Menu
  2. Vasil
    Admin
    Vasil avatar
    1547 posts

    Posted 06 Jan 2014 Link to this post

    Hello Yohan,

    You can use the CheckBox before the item listed in the All Fields, to select it, and it will go to the proper field area. We will try to improve the configuration panel and the fields drag-drop functionality in future to restrict invalid configurations, but currently there is no option that to disable the drag-drop as per your requirements.

    Regards,
    Vasil
    Telerik
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Yohan
    Yohan avatar
    32 posts
    Member since:
    Jan 2014

    Posted 12 Jan 2014 Link to this post

    Hello Vasil,

    Can you mention when exactly this will be fixed? further more is there any patch mechanism where i can problematically disable inappropriate selections from Fields Context Menu in configuration panel? code snippet may be helpful.

    Regards,
    Yohan 
  5. Vasil
    Admin
    Vasil avatar
    1547 posts

    Posted 15 Jan 2014 Link to this post

    Hello Yohan,

    Currently I could not give an estimation when we will improve this or it will be possible to be improved. At the moment there is no workaround.

    Regards,
    Vasil
    Telerik
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
Back to Top