@Ted Phillips - This one is probably for you and your team.
I have logged a support call around this and waiting to hear back.
My experience in PAfE after making master data changes is that there is a missing sync or refresh button/process/check.
Essentially what happens is a new member is added and someone updates the values in the cube against it manually via PAW input or via TI.
Update values can be read in PAW and everything looks good. In PAfE however you receive #VALUE!
Stranger is that a DIMIX is happy to return the index and a DBSW is happy to send a value (as long as you do not try send a reference to a blank cell, but that is an issue for another day)
I can clear my PAfE cache, change DB to another then come back, refresh the task pane, disconnect my session and connect again, all to no avail.
A Refresh sheet/book etc. shows the #VALUE! against that new member.
Only if I close Excel and reopen does this seem to cause the master data to download again - reminiscent of running an "M_Clear" in the old days.
Similar behaviour experienced when adding members to rollups or changing an alias, changes just do not seem to reflect until restart.
Any ideas on what is happening here or am I doing something wrong?
On a related note, tracking down the root cause of the #VALUE! problems is a nightmare. I recently typed in Cost Centres instead of Cost Centre in a DBRW that had 10 arguments. Any one of the 10 could have been invalid, my session could have been disconnected, the server/cube reference could have been invalid etc. etc. etc.
Before logging the idea I was hoping to get insight into whether or not it would be possible to return something more useful than #VALUE! like a reference to the invalid argument(s). Cumulatively across the IBM community this would likely save years of hunting time.
Possible?
Thank you in advance.
------------------------------
George Tonkin
Business Partner
MCI Consultants
Johannesburg
------------------------------