Alan Whitehouse's Ramblings

Continuing to work until my heavy investment in lottery tickets finally pays off….

  • Categories

  • Archives

  • Deep Thought

    Historically speaking, all true change in the world has come thanks to leaders emerging, them taking charge and giving the masses someone to rally around. Can an intentionally "leaderless" movement survive or will it just slowly fade away?

  • Subscribe

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 18 other followers

  • Me!

  • Advertisements
  • Disclaimer

    The views expressed in this blog, while intelligent and always right, are strictly my own, and do not necessarily reflect the views of anyone else with which I am in any way affiliated. And don't forget, I own the rights to all information on this blog (except for the stuff I stole from other people).
  • Current Rant


    You want change, then get involved. Vote, run for office, go to shareholder meetings and contact advertisers or investors. Sitting around banging drums, singing kumbaya, smoking weed and having a camp out under the stars is not going to get you the change you want.

  • Admin Stuff

More Lessons While I Am At It

Posted by Alan on September 25, 2008

Since I get a breather today to get caught up on things like e-mail and a couple other projects here are a couple more lessons learned that have come to mind:

  1. If a user is in two or security roles, the user will receive the permissions that are the MOST LIBERAL and not the most restrictive.   Meaning if onje of your security roles has permission set to NONE for the members of a certain dimension and one of your security roles has permissions set to READ + WRITE for that same dimension, they receive the READ + WRITE permissions.  I personally think this goes against good system security design which should err on the side of caution when a conflict arises.
  2. You will be amazed by the sheer number of times you will open the same form template, tweak it, save it and republish it to get it “just right”.
  3. You can’t get through a project without some form of MDX coding.  It just ain’t gonna happen.
  4. You might get through a project without some VBA coding behind the sceens but don’t count on it.
  5. Believe it or not, you can have enough dimensions and dimension members on a form that it is too large to submit because how the data is parsed in the backend.   This will stress you and the client out to the n-th degree. 

I am sure there will be more along the way.


4 Responses to “More Lessons While I Am At It”

  1. Petert Eb. said

    #3 While on one hand I’m happy about that we designed the addin so that you could use native mdx in reports and forms. On the other I’m curious about what kinds of authoring are not possible via our UI that you might resort to straight mdx?

    Or if this is more rule related, what features are missing from PEL that make you have to do a native mdx rule?

    #5 is it failing to submit (because of a timeout?) or is it failing to whatif because of the 2MB query length?

  2. Alan said


    Here is some insight to what I mean:

    #3. We use the UI to generate the base MDX and then tweak it. We have implemented the cascading rows concept using the assumption sub-model we discussed for two clients so far and based on discussions it will probably come into play for two other clients as well. Given that track record, I see this as a farily common occurance. We are not doing full blown MDX coding but what I would consider tweaks.

    #5. For this current project, we have a model with a lot of dimensions. On one of the input forms we have 3 columns (using the above mentioned cascading filtering) and 2 or 3 rows (I forget right now) and 2 filters. Some of the dimensions only have a dozen or so members while others have 100+ members. The errors we get are the 2MB query length issue.

  3. Peter Eb. said

    Ok yes for #3 cascading filters or linked filter scopes etc are definitely a common request.

    For #5 there is a kind of awkward workaround if you get the error only after data entry. If you don’t need to recalculate to see totals after big data entry (sp1) like that, then you can disable what-if on the matrices. Then at least you can complete the submission, clear the change list (there’s another sp1 option to automatically do that) and then after the submission is processed see the totals… Or are you running into the 2MB limit with the select statement alone?

  4. Alan said

    We have suggested turning off the “what if” but the sheet has some calculated fields on it and the users need to see the finals as part of their checks and balances before they submit. It gets ugly having to ask them to not see changes, do a submit draft, clear changes and then re-open to see if their numbers look right.

    We have also run into the 2MB limit on the select as well I believe, but would have to confirm that specifically.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: