TI Process check if target cell has "rules applied to cell"

[BigG]

I have a TI Process that allows me to copy from one version to another and is reusable in many cubes. I load data from rule calculated cells in one version to STET cells in another (for archiving). But in some cases calculated rule cells will target rule cells causing the "Rule applies to cell" error in TI process.

Does anyone know a TI Process rule I can use to exclude the target cell if a rule is applied?

Thanks in advance

[Alan Kirk]

I have a TI Process that allows me to copy from one version to another and is reusable in many cubes. I load data from rule calculated cells in one version to STET cells in another (for archiving). But in some cases calculated rule cells will target rule cells causing the "Rule applies to cell" error in TI process.

Does anyone know a TI Process rule I can use to exclude the target cell if a rule is applied?

The CellIsUpdateable function? I've never had to use it myself but from the description it should work with rule-calculated cells.

[qml]

I confirm, CellIsUpdateable is the right function for this. I tend to put it in those of my TI's with a longer shelf life to check if someone hasn't put a new rule somewhere where the TI wouldn't normally expect it. This way you can catch the error instead of having the TI fall over.

[BigG]

sweet, sorted... cheers Alan and qml.

[Steve Rowe]

It would be great if you could set the CellPutN/S functions up to fail quietly, that way you could avoid if testing every single piece of data. If you need to check for rules and then check for strings or numbers for every write operation it can start to grind the speed down.
Cheers

[Alan Kirk]

It would be great if you could set the CellPutN/S functions up to fail quietly, that way you could avoid if testing every single piece of data. If you need to check for rules and then check for strings or numbers for every write operation it can start to grind the speed down.

Agreed; an On Error Resume Next-style construct would be useful.

IIRC this type of error constitutes a "Minor" error in TI's view, so it would be possible to suppress any errors by setting MinorErrorLogMax to 0. But of course if you do that then you prevent any legitimate errors like key errors from being reported.