Dim Build Rule Strips Quotes - WHY?

I am trying to build a rollup with member formulas that use double quotes around the member names, but I can't get the load rule to stop stripping out the quotes. I've tried modifying the source text file to use regular quotes, triple double quotes, etc. I can't find a setting to make this stop. Does anyone have a solution? Thanks, James

I'm one of the folks who have answered this before, but I'll post it again here just to make it easier to find. Just use single quotes in the build file where you want double quotes in the formula and in the formula field in the load rule replace the singles with doubles. Remember to select the change all occurrences option.

Similar Messages

How to use substitution variable in case of dim build

Hi all,
Lets say I have 3 sub vars - Prevmonth, prevmonth-1, prevmonth-2. These will change every quarter.
I want to build a cube which will have which will have only the above 3 months in the Fiscal dimension. This will be used once at the end of quarter.
How do I refer substitution variables in case of dim build rule files? I want automate the process. We have SQL dim build for other dims, only this dim can be built from flat file also.
Or is there any other way to achieve this apart from using sub vars? I can try store the 3 variables in a table and then use them to build the cube, but want to see if we can avoid creating one more interface.
Thanks.

Actually using the values of subvars to build a dimension (which I believe is what you want) is a fun problem. Here's an (Oracle) example that would do that, without requiring any additional table or flat file:
 SELECT 'FiscalPeriod' AS Parent,
 CASE Level
 WHEN 1 THEN '&CurrMonth'
 WHEN 2 THEN '&PrevMonth'
 WHEN 3 THEN '&PrevMonthMinusOne'
 END AS Child
 FROM Dual
CONNECT BY Level <= 3
Here's how it looks in the load rule SQL dialog, and the data prep editor:
It's fun because I've never thought about it before, but I don't actually recommend this - if you have other ETL going on in SQL I'd generate the values in a table / view there, and have a script that both updates the subvars and builds the dimension direct from that.

Automate dim build

I am using MaxL and Rules file and I want to; delete all members of a dim, then build it with current text file provided. Are there MaxL commanda for deleting a DIM or can it be done from a rules file? Jim

There is no direct MaxL command to delete a DIM, but you can remove all members of a dim thru a dim build rule and an empty file. Sometimes rather than removing them all it works better to append one dummy member while removing unspecified. If your dim is e.g. dyn calc it will complain if you try to save with no child but it's happy if there is 1 dummy child. Then your rebuild must remove unspecified, that will toast the dummy.

Dim Build Warning

Anyone know what this means?
Data file cache size ==> [0] Kbytes, [0] data file pages
Allocated TRIGMAXMEMSIZE: [4096] Bytes.
Loading New Outline for Database [CP_Ace] Succeeded
Missing Database Config File [D:\Hyperion\products\Essbase\EssbaseServer\APP\CP_Ace\CP_Ace\CP_Ace.cfg], Query logging disabled
Total Restructure Elapsed Time : [2.484] seconds
Object [CP_Ace] unlocked by user [MikeHa]
Database import completed ['CP_Ace'.'CP_Ace']
Output columns prepared: [0]
The rule works, the dim builds, but this warning appears - just wondering what it means. Why might one have a missing Config file?
Thanks for any insight, Mike

I'll guess from the message this is a BSO cube. It just means that query logging is not turned on. It is no big deal. If you want to learn more about Query logginga nd BSO databases, check out the section on it in the tech reference. http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/frameset.htm?launch.htm

Dimension Build Rule converting characters to ascii

Hi
I have a dimension build rule which has been in place over a year. However every few weeks it converts some of the dimension members to ascii characters but loads with the correct alias. The next time the load runs, it tries to enter the real member and it falls over as the alias is not assigned to the member with the ascii characters.
Has anyone seen this before or have any suggestions as to what could be causing it.
Thanks

Have you tried recreating the load rule to see if it's some form of weird corruption?
That doesn't seem very likely (it's either corrupt or it's not <--This is why I Like Computers) -- how about can you confirm that your source is exactly the same both times? I'll bet it's not and you just see the result manifested in the dimension build.
Regards,
Cameron Lackpour

ASO dim build

Every month I build a dimension that may have a few new members added. I am getting a lot of these error messages, \\Record #760 - Property [Location] changes for member [BBDX] not allowed (3315) The new members are getting added and the error messages are from members that already exist. What is it from and how can I get rid of this error message? (The dim build file will contain the complete dim hierarchy every month, I can't just load a file w/ new members) Jim

Jim: In your load rule you must be setting a property - like a consolidation operator, storage setting, or attribute - on your members. When you run the rule the next time and Essbase sees the property already set on the member and a non-blank field in your data source for the member's property, it treats that as a "property change", even though there is nothing changed. Example: The first time you run a dimbuild, you set member ABC with the consolidation operator '+'; it sets it as it should - life is good. Next time, when Essbase gets to the same member, it says to itself "hmmm...I'm being told to set the property on 'ABC' as a '+', but it's already set. I don't see the 'Allow Property Changes' checkbox being set, so I'll not set the property again, throw an error and move on." Essbase, in all its wisdom, is unable to tell that changing a '+' to a '+' isn't a change - it simply sees a non-blank proprety field in the source data and throws the error. Make the problem go away by checking the 'Allow Property Changes' box in the Dimension Build Settings dialog. That's it!

'Invalid Dim' error during dynamic dim building

Hi Folks,
I am trying to update an outline using my own dim rules file and data .txt file, but i get an error in the dimbuild log file saying "\\Column 7 - Invalid Dimension" What could be the reason for this? The outline already contains 5 standard dims (i.e. Customer, Period, Account, Scenario and Year) and 2 more attribute dims. My goal is to add some new members to the existing Account dim. My data file looks like this:
Account,Metrics,,O,~
Metrics, Avg_Wolverines_Juggled, Average Wolverines Juggled, S,~
Metrics, Avg_Dropped_Wolverines, Average Dropped Wolverines, S,~
Metrics,Headcount,,S,~
In the data-prep editor I have created a .rul file that has 6 columns (fields). The first field I created by mistake, so I have set it to 'ignore field..' under 'dim build properties'. The next 5 fields map correctly to the way I have arranged my data file, i.e Parent0, Account Child0, Account Alias0, Account Property0, Account Property0, Account
This .rul file validates correctly, but when I try to update the outline, I get the "\\Column 7 - Invalid Dimension" error log message. The log msg says that the data file contains an error, but may have partially loaded data. However, I don't see a SINGLE new member added to the outline..
In terms of settings, everything under 'Dim Build Properties' seems fine. i.e. for each field the correct dim type (e.g. Parent, Child, Alias, or Property) and dim name (i.e. Account) is selected. However, under 'Dim Build Settings', when i try to choose 'Account' as the dim name, it reverts back to the name of the first dim in the outline (i.e. Customer) whenever I close/reopen 'Dim Build Settings' This happens even though I do a double-click and make sure 'Account' is shown in Blue before closing out of 'Dim Build Settings' Could this have something to do with the error I am getting? I have also made sure that the 'Build Method' is correct (i.e. Parent/Child references) for the two main dim fields. As per my understanding, for alias and properties fields, the Build Method doesn't matter.
I apologize for the long question, but would really appreciate some help.
thanks,
Akshay

Ah good old wolvering Juggling. The problem is they will bite you if you are not careful. (It's a nice metaphor for essbase). learning from Edwards book I see.
your file looks like it only has five columns and you say you created a sixth column that you set to ignore. The message indicates there is a 7th column. Open your load rule and your data file and see if in fact there is a trailing column. Also, make sure you set the dimension build properties for the account dimension to be parent/child

Dim Build Error

There isn't any keywords or reserved words for dimensions, are there?
I'm building dimensions from a sql call, it creates all of them except for "OTHER" which gives the following error:
\\Record #10 - Incorrect Dimension (Region) for Member OTHER (3308) OTHER

This is a common problem in the essbase world and a reason many cubes have prefixing. Unless you are working in system 9.3 and have elected to allow duplicate names, you have simply used the name other twice in two different dimensions.
This is confusing to those with a relational database background because Other Region should be different from Other Product and Other Customer. You need to remember that the labels such as Othe can be used by an end user at anytime in any position. So you need to make each label in your database unique. The time tested process is to prefix (or suffix) all the members within a dimension. So all of your products could be prefixed with a P and all of your regions with an R. Or you could prefix with Prod or Product. As the moment you are only having the issue with Other, but it could happen when you have a saleman named West and a region West, etc. So the prefix solution allows you to have things run on autopilot.
Two other options, in the dimension build rule, you could change Other to Other Region. This is the easiest solution for a business owned application.
The other choice is to change your ETL so Other Region comes in your file as Other Region.

Error in invoking the build rule editor, LabView 2011

Hi all. I'm having a problem in Project Explorer. When I right-click on 'Build Specifications' and select New:Application (EXE), I get the following error dialog:
"There was an error in invoking the build rule editor. Please check the corresponding provider directory to see if any VIs are broken."
After this appears, no build specification is created.
I built this application in LabView 2010 on WinXP and was able to compile and run it sucessfully many times over the last few weeks.
The problem started yesterday when I had a problem with a Ring control. I right-clicked it and selected "Edit items" or "Properties" the cursor blinked for a moment but the dialog box did not appear. I removed the Ring control and replaced it with a String control, then when I tried to build the application, I got this error message. At that time, I also noticed that I could not get a Properties dialog box to appear for any controls or indicators.
Yesterday, I installed NI Developer Suite 2011 Version DS2. This seems to have fixed the problem with the dialog boxes and I was able to use the Ring control. However, I still have the problem with the build rule editor.
To determine if there was a problem in my program, I built a new 'Hello World' .vi with just a string control and string indicator. This program has the same problem when trying to build to an .exe.
Currently, I am trying to remove all previous versions of LabView. When that is done, I will reboot and try to build again. If that doesn't work, I will remove ALL National Instruments software and re-install NI Developer Suite 2011 DS2.
I'm hoping someone can provide a solution before it comes to that.
Two other facts which might be relevant: I don't have Administrator on this machine, although I could probably get it if I could make a strong case. Also, I can't be sure, but I think the problem may have started when I undocked my laptop from the docking station to go to a meeting.
I appreciate your help. Thanks in advance.

If you need additional assistance, I encourage you to create a new thread. It is more likely to be answered by other users as a fresh post.
The most likely cause is a corrupted file (or files) in the builder directory.
I would recommend renaming/moving the following folders and performing a repair install of LabVIEW:
\National Instruments\LabVIEW 2011\vi.lib\AppBuilder
\National Instruments\LabVIEW 2011\resource
Regards,
AnjelicaW.
Regards,
Anjelica W.
National Instruments
Applications Engineer

MAXL - using multiple Dimension build rules in single script...

I seem to be having problems running multiple Dimension build rules in a single MAXL script, is this a known problem or just an issue that I'm having? The build rules independently work as designed but when joined into a single script the script hangs...
So, this is a 2 part question...
1) Does MAXL not play nice when using multiple Dimension load rules in a single script?
2) Do I need to run the build rules independent of each other?
Also, is there some type of refresh/update on the cube that you can use in the script and would it be necessary...?
Thanks for any light you can shed on the issue.
Adam,

I've written multiple dimension build statements as a part of 1 long MaxL statement. I'm executing this MaxL via a shell script (that replaces the variables such as username, password, servername, file path etc.) I've not seen any issues doing so.
However, I've noted that, number of imports statements in 1 single MaxL command does not bode well for more than *60* import statements at once. So, if you're using more than 60 source files to build your dimensions, please consider breaking up your MaxL into multiple statements.
Note: All but last of the import statements have 'deferred' re-structure specified. It speeds up the build process.

Freight Unit Building rule isn't used when FWO is automatically created via PI

a freight unit building rule is created and attached to the forwarding order configuration , When forwarding order is created manually , Freight unit building rule is picked up automatically , and freight units are created based on such definition.
When Forwarding order is created via PI , the freight unit building rule isn't picked , I need it to be picked in all cases.

Hello,
You can check your condition /SCMTMS/FWO_TYPE and check, which type FWO was generated by PI. If you have more than 1 type.
Maybe you FUBR was assigned in FWO type 2 and PI creates FWO type 1 (Standard selection).
Could you check this?
Best regards,
Vicente Picard

Setting member properties through Build rule.

I have a hierarchy where the product structure needs to be updated.
Now, I also need to add three different UDAs to each member.. and make some members Never share. (All in build rule)
Please suggest me with any solutions.
TIA,
KRIS.

To set the data storage you need to set the column field type to property in the rule file and then the value in the record to set to datastorage to "Never Share" will be N
A list of properties are available at :- http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotrules.html#dotrules_2
Also there is detailed information about building load rules
You would set the column to UDA field type for UDAs
An example parent/child build to set a member to "Never Share" and set UDAs would be
Parent,Child,Datastorage,UDA1,UDA2
Prod,ProdA,N,UDAName1,UDAName2
Your load rule for a parent/child build would look something like
PARENT0,Product Child0,Product Property0,Product UDA0,Product UDA0,Product
Prod ProdA N UDAName1 UDAName2
Cheers
John
http://john-goodwin.blogspot.com/

Remove quotes from the data when building rule file

I get double quotes in one of the field in the file. e.g. Part descirpiton as inches. I have to join part number and part descrption to create one field and create level 0 dimension. When I try to replace " with space after joining the two fields, it does not replace the quotes. If I replace it first and then join the fields, it gives me error "The field type for this field is not valid for the build method associated with this field's dimension."
What am I doing wrong?
Thanks
Please help.

A double quote is one of the problem children of Essbase. If this is coming in from SQL, you could do a replace on the character to remove it. If it is a flat file, if it is always in the same location, you could split the field on the character and ignore it. It has been a long time since I've had to deal with the problem, but I think I ran my file through some preprocessing to remove it.

Dimension Build Rule Null Processing

Hi There,
I try to build Dimension Rule file with Generation build, I have Gen2, Gen3, Gen4, Gen5, Gen6, but some only goes to Gen3, so I check Null Processing, hoping this will take care of the issue.
However, I still got error "Child Member 368 with no parent"
I am using txt file as source.
wondering what I do wrong here, is this because Essbase think it is the space, not null value?
Thanks in advance.

Try to put a '\' before ".
You're formula will be
@RELATIVE(\"Dim Name\",0)
make these changes in the flat file or table and then try build the dimension.
Regards,
RSG
Edited by: RSG on Mar 20, 2012 10:37 AM

HELP!! MY IPOD SCREEN DIMMED WITH WHITE STRIPES AND BLACK BACKGROUND

im wake up this morning and find out that my ipod got boot loop, it's stuck in apple logo. i try to connect it to itunes and reset it. its work, i can hear charging sounds, and unlock sounds. and also im trying to test camera and seems it worked (i can hear camera sounds) and after taking 1 picture, the camera show up but with these stripes, but i cant access picture library. but when im looking at the screen, i just see black screen with dim white stripes in the middle. i was thinking if my screen just broke or something. but the apple logo appear good without any scratch or stripes.
Here's the picture
these stripe dim alternately. i only can see these two stripe
Some one please help me about this problem. i have no idea how to fix this. sorry for my bad english

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

Dim Build Rule Strips Quotes - WHY?

Similar Messages

Maybe you are looking for