Dear visitor, welcome to Palo Community Forum.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
Make sure to enable screenupdating in the import dialog. Then click on NEXT instead of FINISH. If there is something written by your PALO.SETDATA Formula you will see the value that is written in the formula cell. If there is an error (unknown elements e.g.) in your PALO.SETDATA it will return something like #NV. Did you seee something like this?
Then there must be an error in your PALO.SETDATA formula because usually you see the value that is written. Can you attach a screenshot with cellfocus on PALO.SETDATA Cell during import process? That would help.
So your Cube "Market" (which must already exist) should have the following dimensions in that order:
Months
Years
Regions
Datatypes
Measures
Products
Is that right?
Did you try to execute one single PALO.SETDATA with hardcoded element names (recalc with F9) ? What happens then? Maybe its an excel autoformatting issue e.g. 2002 instead of "2002"...
Writing it to the original Sales cube would look like this:
=PALO.SETDATA(4711;FALSCH;"localhost/Demo";"Sales";"Notebook SX";"Austria";"Apr";"2002";"Actual";"Units")
After that you should see the value 4711 in this cell and the value should have been written to PALO.
Maybe you should activate Excel Auto-Calculation in Options-Menu before importing with the wizard....
Nice to hear. So check your calculation options in excel (turn it to automaically) and the formatting of the cells you reference when using the wizard.
Okay,
so here is my last idea before suggesting to reinstall the client :-) but I hope thats it:
As i can imagine (from your screenshot) you write the value in Cell G1. If this is a formula that says like "=F1" its possible that excel hasn't calculated it yet at the time the PALO.SETDAZA is fired. Try to use F1 in you PALO.SETDATA formulaand E1 instead of E2.
Holger
This post has been edited 1 times, last edit by "h_decker" (Oct 24th 2007, 2:13pm)