You are not logged in.

Cannot use string returned by PALO.DATA as argument in another PALO.DATA

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.

ckosiegbu

Professional

  • "ckosiegbu" started this thread

Posts: 14

Date of registration: Apr 10th 2012

  • Send private message

1

Tuesday, June 19th 2012, 12:18am

Cannot use string returned by PALO.DATA as argument in another PALO.DATA

Hi,

I have noticed that if I have a rule that returns a string value from a cube using PALO.DATA, this string that is returned cannot be successfully used as a value in another PALO.DATA rule. For example

Source code

 
1

[string] = PALO.DATA(.....)



Source code

 
1

[measure] = PALO.DATA (database, cube, dimension1, dimension2, [string])



The 2nd rule doesnt work for some reason. If [string] is replaced by a hard-coded value it works. However, this is not an option for me for me because I have to lookup the string values from a reference cube.

Can anyone help?

Regards,
CK

ethssn

Master

  • "ethssn" is male

Posts: 54

Date of registration: Feb 16th 2012

Location: Hamburg

Occupation: BI-Consultant

  • Send private message

2

Tuesday, June 19th 2012, 1:55pm

Did you type the rule or generate it via advanced editor (only available inside XLS-Addin, not on web/OLAP-Manager)? If you could reference your cell, where the rule-aquired string is "stored", you might figure out the correct syntax this way...

Best regards,
Stefan

h_decker

Sage

  • "h_decker" is male

Posts: 763

Date of registration: Oct 26th 2005

Location: Cologne, Germany

  • Send private message

3

Tuesday, June 19th 2012, 5:09pm

Hi CK,

there should be a toString-Function or something similar (think it is simply STR()). Try to wrap your PALO.DATA with that.

Holger

ckosiegbu

Professional

  • "ckosiegbu" started this thread

Posts: 14

Date of registration: Apr 10th 2012

  • Send private message

4

Tuesday, June 19th 2012, 10:30pm

Hi Holger,

Thanks for the feedback. STR() works on an integer and converts it to a string. I don't think that will work in this case because the value I'm looking up is already a string. I did try TRIM() though on the off chance that the string value being looked up was coming back with blank spaces at the end. It didn't solve the problem.

The real problem I'm facing can be seen in the two screenshots below. There shouldn't be a difference between the results for the two sets of rules. However, as you can see from the screenshots, there is. Any ideas why?

Regards,
CK
ckosiegbu has attached the following images:
  • Screen Shot 2012-06-19 at 21.18.01.png
  • Screen Shot 2012-06-19 at 21.18.59.png
ckosiegbu has attached the following files:
  • Total.zip (58.9 kB - 27 times downloaded - latest: May 13th 2013, 8:44am)
  • AllocationRules.zip (18.71 kB - 38 times downloaded - latest: May 13th 2013, 6:56pm)

This post has been edited 1 times, last edit by "ckosiegbu" (Jun 19th 2012, 10:47pm)

h_decker

Sage

  • "h_decker" is male

Posts: 763

Date of registration: Oct 26th 2005

Location: Cologne, Germany

  • Send private message

5

Wednesday, June 20th 2012, 9:45am

Hi CK,
what should I say. Works for me :-) See Screenshot. (Jedox for Excel 3.3 build 5751).

Holger
h_decker has attached the following image:
  • palorulefactor.png

ckosiegbu

Professional

  • "ckosiegbu" started this thread

Posts: 14

Date of registration: Apr 10th 2012

  • Send private message

6

Wednesday, June 20th 2012, 3:06pm

Thanks Holger,

I guess this is a bug in Palo then. I wonder if a more recent version with this problem fixed is due out soon.

Regards,

CK

tish1

Sage

Posts: 761

Date of registration: Jul 13th 2009

Location: Vienna / Austria

Occupation: Senior Consultant @ Vector SW DV GmbH

  • Send private message

7

Friday, June 22nd 2012, 3:07pm

Hi,

can you try to use a second PALO.DATA formula instread of the cube reference "[string]". The behaviour might be different.

Source code

 
1
2
3

[measure] = PALO.DATA (database, cube, dimension1, dimension2, PALO.DATA (database, cube, dimension1, dimension2, string))
instead of
[measure] = PALO.DATA (database, cube, dimension1, dimension2, [string])


Regards.
Robert Tischler
Senior Consultant Vector SW DV GmbH

ckosiegbu

Professional

  • "ckosiegbu" started this thread

Posts: 14

Date of registration: Apr 10th 2012

  • Send private message

8

Friday, June 22nd 2012, 4:18pm

Hi Robert,

That was the first option I tried. The result was the same as using the cube reference.

Regards,

CK

Similar threads

Rate this thread