Hi all,

I hope this message finds you well.

I'm encountering an issue with a chore that runs an export process for cube data. The process is designed to export the data from the cube, and I've noticed the following behavior:

• When I manually run the export process, it works perfectly, exporting all the data with no issues.
• Similarly, if I manually run the chore that includes this process, everything functions correctly and the data is exported as expected.
• However, when the chore is triggered by its schedule, the process runs but no values are exported for the records.

I'm puzzled by this discrepancy and would appreciate any insights or suggestions from the community and the PAW development team.

Has anyone experienced a similar issue? Are there specific settings or considerations for chore-scheduled processes that might be causing this?

Thank you in advance for your help!

Cheers, Asgeir

------------------------------
Asgeir Thorgeirsson
------------------------------

Unfortunately, the StringToNumber trick did not work for me.  It appears as though the view is just not getting generated at all.

Hi Asgeir, 

I am experiencing the same issue, with a process that creates a view and generates an email to report any changes from a snapshot.  Your description of the issue is exactly the same.  I have a support ticket open at the moment for IBM to look into this.  

I will try your 'String' resolution as a temporary fix.  

Thanks,

Hi Craig,

Here is a snippet that may help (from the old perspectives wizard).

if (VALUE_IS_STRING=1,CellPutS(SVALUE,........, CellPutN(NVALUE, ...);

One other thing to check is:

If the strings are created by a rule, are they fed correctly.

Jules

------------------------------
Julian Sedgewick
------------------------------

Hi Asgeir

I experience the same problem but only for some of my data. I have a chore with 3 export processes and only 2 of them have this problem.

 Have you raised this with IBM Support as it seems like a bug?

------------------------------
Jesper Poulsen
------------------------------

Apparently there is a potential problem with MDX views as source.

My workaround was as simple as yours;  vExportValue = NVALUE;

Hi Jesper, 

So I raised a ticket with IBM when I first experienced this issue.  After 68 days with IBM support and no resolution, I was finally able to solve it myself.

I played with the dimension placement, and ended up with a an MDX statement (uses a calculated WITH MEMBER) with only a 1 element column and it worked, prior to this I was using an MDX statement with a 3 element set in the columns and it would return nothing when run via a chore.  Still no idea why it works when run manually with multiple columns but fails via a chore.  IBM only closed my case, not sure if it was passed on to the developers to find an answer/fix.

I'm not sure if this is possible for your situation, but it worked for me.

Regards,