In Pafe when a user executes a DBS against a cell which is not writeable the formula returns the value of the cell. Not writeable means C level, read-only access, write access but locked.
This is counter productive, the job of the formula is to send data to TM1 and report success or failure.
There is now no difference in cell state between the formula successfully working or not. This means that in Pafe every DBS execution needs full reconciliation post send to test for success, this should not be required.
In the legacy clients sending to a non-writeable cell meant that the formula showed an error, a clear and obvious indication of a fault.
Imagine designing TI processes such that they always report success and suppress all error messages. Makes no sense, the same logic as to why a TI process has errors and so forth applies to DBS formula.
|Who would benefit from this IDEA?||Users would benefit as they can tell what they are doing is working. BAU temas would benefit as they will get fewer queries about why reports are showing incorrect values. TM1 would benefit from the lack of reputational damage from having illogical / dangerous functionality.|
How should it work?
Sending values to a non-writeable cell should retun #N/A giving the user a clear indication that there is an issue with their access.
|Priority Justification||Ongoing risks to system integrity plus request from high value customer.|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions