.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Sharon Maxwell
Post New Web Links

MDX Script: overriding cells

Posted By:      Posted Date: September 23, 2010    Points: 0   Category :Sql Server
 

hi all, I have a pesky MDX script issue whereas I want to override the [(All)] level for a dimension, to basically blank out the 'totals' -- and it works great, using the code below:


SCOPE
  ([Owner Curr].[Emp Curr].[(All)],
     MeasureGroupMeasures('Sales'));
  THIS = NULL ;
END SCOPE;

The problem that I have is that I'd like to do the same totals override on a similar dimension (same dimension structure but different data, a historical parent-child dimension) however, coding similarly (below) invalidates all cells when drilling into [Owner Hist].

SCOPE
  ([Owner Hist].[Emp Hist].[All],
     MeasureGroupMeasures('Sales'));
  THIS = NULL ;
END SCOPE;

My hypothesis is that, that is so, because the [Owner Curr] when not drilled into (drilling into [Owner Hist] only) assumes it's at the default [All] level and blanks out everything, hence also the [Owner Hist] cells. 

Am I overlooking something simple?

thanks a big bunch -- Cos.

 

 




View Complete Post


More Related Resource Links

Edit GridView Individual Cells in ASP.NET

  
The ASP.NET GridView allows for a row of data to be edited by setting the EditIndex property of the GridView, placing the entire row in edit mode.

You may not want the entire row in edit mode if you are using DropDownList controls for several columns in the EditItemTemplate. If each DropDownList has many options then loading them all at once may result in a sluggish page. Also, if your data structure is more like a 2 dimensional array rather than a set of rows, you may want to edit each cell individually.

Here I will demonstrate how to achieve this and also how to deal with event validation without disabling it.

Edit Individual GridView Cells in ASP.NET

  
The ASP.NET GridView allows for a row of data to be edited by setting the EditIndex property of the GridView, placing the entire row in edit mode.

You may not want the entire row in edit mode if you are using DropDownList controls for several columns in the EditItemTemplate. If each DropDownList has many options, then loading them all at once may result in a sluggish page. Also, if your data structure is more like a 2 dimensional array rather than a set of rows, you may want to edit each cell individually.

Rendering ASP.NET Script References into the Html Header

  
One thing that I've come to appreciate in control development in ASP.NET that use JavaScript is the ability to have more control over script and script include placement than ASP.NET provides natively. Specifically in ASP.NET you can use either the ClientScriptManager or ScriptManager to embed scripts and script references into pages via code.

*.axd script references not being rendered to browser

  

I'm running VS2010 with .net 4.0, and am running into issues with the .net ajax script tags mysteriously not being rendered to the browser.

So far I've reduced it to a scenario where I set the DataSourceID property of a databound control.  More specifically, I've only tested it on a Gridview and a DropDownList.

This can be reproduced fairly easily on my machine by following these steps:


1. Create a new empty Web Application Project

2. Create a new Web Form

3. Add a ScriptManager inside the form

4. Add a DropDownList and a DataSource (I used an ObjectDataSource)

5. Set the DataSourceID property of the DropDownList to the ID of the DataSource.  This can be done either declaratively on the .aspx page, or in the code behind in the aspx.cs page, and both produce the same results.

6. Open the page in a browser and watch as you get a javascript error stating "Sys is not defined" and notice that the page source contains no script tags referencing *.axd scripts.


Here's my source code showing my set up:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="ScriptResourceFAIL.Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 T

Client script not running

  

Dear all,

in my MVC 2 application, and in the shared Master Page I wrote this little script for menu handling :

<script src="../../Scripts/jquery-1.4.1.js" type="text/javascript"></script>
<script type="text/javascript"> $(document).ready(function () {   
       
     $('#nav li').hover(  
         function () {  
             //show its submenu  
             $('ul', this).slideDown(100);  
   
         },   
        function () {  
           //hide its submenu  
            $('ul', this).slideUp(100);           
         }  
     );  
       
 });</script>


The script, that shows menu items when the

Potentially dangerous script....blah blah

  

explain this one - -   (please)

2 projects - same code - one, using 2008, one using 2010 - a textbox a button and a label, using html code in the textbox

In the Page Directive:
EnableEventValidation="false" ValidateRequest="false&q

Cutting Edge: Subclassing and Overriding ASP.NET Pages-Part I

  

There are a number of techniques that allow you to modify a running ASP.NET page without touching its source code. Dino discusses some this month.

Dino Esposito

MSDN Magazine April 2007


Cutting Edge: Custom Script Callbacks in ASP.NET

  

ASP. NET client callbacks represent a neat and elegant way to execute server-side code without posting and refreshing the current page. I discussed ASP. NET callbacks in the August and December 2004 installments of Cutting Edge, considering them from the perspective of rendered pages making background callbacks to the server, sending input data to the relevant page, and receiving a response.

Dino Esposito

MSDN Magazine January 2005


Cutting Edge: Implications of Script Callbacks in ASP.NET

  

Script callbacks in ASP. NET 2. 0 is a feature whose time has come. Script callbacks can significantly speed up an application by limiting server postbacks. They also allow you to execute small portions of server-side code without having to manage the view state for reading or writing.

Dino Esposito

MSDN Magazine December 2004


Cutting Edge: Script Callbacks in ASP.NET

  

If you're involved in Web development you may have faced a problem that you couldn't find a good solution for-making client-to-server calls outside the current page. For example, you might want to validate the content of a textbox against data stored on the server asynchronously, without interrupting the continuity of the work or without forcing a full page refresh, which is particularly heavy for UI-rich pages.

Dino Esposito

MSDN Magazine August 2004


Web Q&A: Who Called the Script?, Concatenating Binary Files, and More

  

This month find out which part of an HTML document has called a script, how to concatenate binary files, find a node, reference one script from another, build a GUI database front end in Access, and compare XML files.

Edited by Nancy Michell

MSDN Magazine August 2003


Scripting: Windows Script Host 5.6 Boasts Windows XP Integration, Security, New Object Model

  

Windows Script Host (WSH) 5.6, a major upgrade for the WSH environment, provides some significant improvements over previous versions. A brand new security model that is tightly integrated with security in Windows XP allows administrators to place fine-grained restrictions on scripts reducing the risk from malicious code. In addition, local scripts can now run on remote machines, and enhancements to the object model reduce the amount of boilerplate code needed when writing professional code. This overview of WSH 5.6 explains these changes and how .NET and scripting work together.

Dino Esposito

MSDN Magazine May 2002


Windows Script Host: New Code-Signing Features Protect Against Malicious Scripts

  

Downloading scripts from the Web or e-mail leaves users vulnerable to security risks because scripts can't be signed. But now developers can use Windows Script Host (WSH) to hash scripts so users can verify their source and safety. With WSH, scripts can be signed or verified using all the same tools ordinarily used to sign EXE, CAB, DLL, and OCX files. This article discusses public-key cryptosystems, the process of signing and verifying scripts in WSH, and several warnings about attacks that could potentially be made against cryptographically secured scripts and ways in which to avoid them.

Eric Lippert

MSDN Magazine April 2001


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend