TM1 Forum

Apologies for the cross-post but looking for some answers.

I have a macro that loops through files in a folder containing a Quick Report, opens them then does:

Reporting.GetCurrentReport(ActiveCell).Commit True
Reporting.Wait

(all required modules and classes are configured as the Reporting calls complete without error and commit data, sometimes)

A few lines below I have a DBSS to send a new Status and the Time to the same cube on two separate lines using Application.Run("DBSS",...)

What seems to happen is the Status DBSS fails with Error 2042 - DBSS is using valid parameters and I am Admin.
The Time DBSS seems to be successful and the values are updated in the cube.

Where my logic and sanity start waning is that the process does not always fail.

If I open Excel and log into PAfE then open the macro book and run, everything is committed and updated without error.
If I run the same process again and again, I get the Error 2042 and values do not seem to be committed or updated.
If I send "1Submitted" instead of "Submitted", I do not get the Error 2042 and the cube is updated.
If I use a DBS, which is wrong, it does not work but per previous point, confused why adding a prefix of "1" in my DBSS somehow makes it work.

I have also tried adding CognosOfficeAutomationObject.ClearCache after opening each book to process but does nothing to help my cause.
I have also tried adding additional pauses/wait/sleeps after each DBSS but to no avail.

Anyone come across this kind of thing yet?

Using PAfE 2.0.67.7, no other add-ins running.

p.s. I have opened a case with IBM.

gtonkin wrote: ↑Fri Oct 01, 2021 1:44 pm If I send "1Submitted" instead of "Submitted", I do not get the Error 2042 and the cube is updated.

Does the error only happen if you do a DBSS with the same value that is in the cell already and the error message is really telling you hey I didn't need to do anything? Or perhaps "it" thinks it failed because the value before and after the operation is the same?

Steve Rowe wrote: ↑Fri Oct 01, 2021 10:38 pm

gtonkin wrote: ↑Fri Oct 01, 2021 1:44 pm If I send "1Submitted" instead of "Submitted", I do not get the Error 2042 and the cube is updated.

Does the error only happen if you do a DBSS with the same value that is in the cell already and the error message is really telling you hey I didn't need to do anything? Or perhaps "it" thinks it failed because the value before and after the operation is the same?

Thanks for the feedback.

The error seems to be a bit random - at first it looked like it was happening on the first timesheet and the first DBSS but does not look like it has anything to do with dirty/caching.

However, saying that, it does "feel" like the underlying update issue could have something to do with how dirty/caching is being dealt with.
More often than not, it seems like if we open cleanly, run through a handful of timesheets, everything updates as expected.
If we then clear the data in PAW and rerun the same process with the same timesheets we get mixed results - sometimes only the timestamp is written, sometimes only the data via the commit.