ViewExtractSkipRuleValuesSet Problem

[Malcolm MacDonnell]

Hi All,

Since upgrading to 9.1 SR3 from 8 I have seen a problem at a few different clients where ViewExtractSkipRuleValuesSet doesn't seem to work anymore. In a typical scenario we would build a view in TI and zero it out with ViewZeroOut before uploading data into it. Now we get the error "Error: ... Cell is not writeable". I've tried ViewExtractSkipRuleValuesSet, the older ViewSetSkipRuleValues and also going into the Export as ASCII window and checking the Skip Rule Calculated Values box. Yes I did have '1' for my flag.

None of these work. I have a workaround - using the view as a datasource and writing 0's with an IFCELLISUPDATEABLE test first, but this causes some processes to have to be split into two.

To simplify the TI as much as possible (to isolate where the error is) I built an N-level view (including some rule calculated cells) in the cube viewer and created a TI with just 2 lines in the prolog:

ViewExtractSkipRuleValuesSet ('ca_data', 'zero', 1);
ViewZeroOut ('ca_data','zero');

I still get this error.

I would be surprised if nobody else has come across this as I can repeat it so easily, but a quick search on the forum didn't show anything. Does anyone have any knowledge/ideas on this?

Thanks

[John Hobson]

How odd (or on reflection, perhaps not )

This very thing came up this week with a client, but as I am on holiday, once I had identified the cause I asked them to report it as a bug and let me know what Iboglix came back with.
(Of course I have no idea if they have or what any rsponse was as in the new Iboglix world consultants and clients can't share info like this )

Yup 9.1.3 as well.

Have you reported it Mal, and if so what was the response.

Thanks you for the workaround - saved a bit of head scratching for me there in all probability.

These flags for calculated / consolidated status have been a ROYAL PITA for YEARS.

Thanks again Malcolm.

Best wishes

Johne

[Malcolm MacDonnell]

Hi John,

No, I haven't reported it yet but will do so. I'll test it on SR4 first as I expect that to be the first response

Cheers
Mal

[paulsimon]

Malcolm

Just to confirm, we have had the same problem in the same version.

Regards

Paul Simon

[mattgoff]

I'm pretty sure I brought this problem up with Cognos, but looking back through Insight I never opened a bug... I'm running 9.1 SP4 and the problem is still there. It logs an error to the message log but the Chore reports success when run interactively.

Matt

[Paul Coggan]

Update on the status of this issue is that we registered it as an issue and Cognos has delivered a fix in 9.4 MR1. They are now considering also fixing it in 9.1 (which is what we need). It sounds like the issue is related to rules with a result = STET, within the cube view that is being zeroed out.

[John Hobson]

They are now considering also fixing it in 9.1 (which is what we need)

Where is the "head in hands" smiley when you need it?

"considering"? What is to consider?

[paulsimon]

Hi

Just encountered this same bug in 10.1.1

Code: Select all

ViewExtractSkipRuleValuesSet( pCube , cZeroOutView , 1 );
ViewExtractSkipCalcsSet( pCube , cZeroOutView , 1 );
ViewExtractSkipZeroesSet( pCube , cZeroOutView , 1);

ViewSubsetAssign(pCube, cZeroOutView, pVerScenDim, cZeroOutVerSubset);

ViewZeroOut(pCube,cZeroOutView);

Wouldn't it be nice is bugs stayed fixed.

Paul Simon

[paulsimon]

Hi

For the record, another post helped on this. I opened the rules added a space and saved them. Then the process ran OK, ie it zeroed out the cube and run successfully without producing a Cell is not writeable error.

Regards

Paul Simon