Testing for a valid cell when using OLAPCellWriteBufferWriteNumberDynamic

Anyone have a good way of testing an OLAPCellWriteBufferWriteNumberDynamic call prior to adding the command to the buffer? Im automating a load of MDAC rights based on user supplied data. I want to ignore any invalid cells. Thought about doing a try/catch on OLAPWriteBuffer with the current member and if it fails, skip adding it to the buffer but it seems a bit overkill and wonder if anyone has a more eloquent solution.

Thanks.

Find more posts tagged with

Infor EPM Discussions

Comments

Martin Reischl

Hi Matthew,

I don't think this approach will work since there will be no error raised when you write the value into the buffer but when you commit the buffer. And it is "all or nothing", an error will mean that none of your values will get written.

What I would do in your case, is to read the valid elements into dictionaries before you start loading the data. Then check against the dictionaries to see if your value will be accepted. Only write valid data into the buffer.

But there may be better solutions out there?

Best Regards

Martin

thomas-neuboeck

This might work for non-existing elements, but would still not catch elements which are readable but not writeable within the user context.

I'd suggest to try if the OLAP AE function might be an option:

OLAPIsCellWritable

Declaration

bool OLAPIsCellWritable(OLAPConnection connection, string cube, StringDictionary cell)

Description

Returns true if a cell is writable.

Martin Reischl

Good point, thanks Thomas.

Whenn writing to MDAC, non-existing elements are the only issue I can think of. You have to be an administrator in order to write to MDAC. And you can write to any element type. Only thing you can't write is invalid values.

But in other contexts, your proposal is great. Only concern is performance - you'll have lots of single-cell requests. You'll probably lose a lot of the benefit of the "buffered" write command just checking if you can write to the cell.

Best Regards

Martin

Nathan Hewat

Hi Martin

I've used the pattern you describe and found it to be relatively straightforward to implement and lightning fast...

It can be implemented using either Dictionaries, Arrays, or StringLists though. Do you have any ideas or opinions on the Pros/Cons of using the different data structures for this particular use case?

Best

Nathan

Martin Reischl

Hi Nathan,

the real question is which is fastest. Honestly, I have no idea. I guessed the dictionary since searching them is what they are here for, but I'm not sure.

Can someone from Development step in here? This would be very interesting to know for me too, and certainly for others.

Martin

Legacy Contributor

Thomas, Thanks for this but Im struggling to understand the syntax of OLAPIsCellWritable. I keep getting the error "Invalid Dimension #FinanceDimension1" using this code (sDim and sFile are arguments passed in:

int iVal = 0;
StringList slCoord = CreateStringList();
string sValue = "";
double dValue = 0;
bool bCellExist = false;

RepositoryConnection repCon = CreateRepositoryConnectionExisting();
OLAPConnection con = OLAPCreateNamedConnection(alias);

StringListList sllCSV = RepositoryReadCsvFile(repCon, sFile);
StringDictionary sdCSV = CreateStringDictionary();

int i = 0;
foreach(StringList slLine in sllCSV) {
iVal = Count(slLine)-1;
i = i+1;
if(i==1) { continue; }

sValue = slLine[iVal];
dValue = ToDouble(sValue);
slCoord = slLine;
Remove(slCoord, iVal);

sdCSV[sDim] = slCoord[0];
bCellExist = OLAPIsCellWritable(con, "GLTOT", sdCSV);
}

}

Legacy Contributor

I found my issue. resolution was:

sdCSV[sDim.Replace("#","",true)] = slCoord[0];
bCellExist = OLAPIsCellWritable(con, "GLTOT", sdCSV);

The Cube was the MDAC, "#GLTOT_AccountingEntity" and the Dimension needed to be "GLTOT_AccountingEntity".

Once I fixed that the rules loaded as expected and I used the bCellExist variable to skip adding the cells to the buffer that didnt exist.

thanks agian.

Copyright © 2025 Infor. All rights reserved.