Another frustrating mystery… I’m using a dataview-condition to compare the current row in the grid as a filter in the dataview. (I would like to find a better solution, but after several hours, I’m starting to get creative).
Things that don’t seem to work.
Expressions like this where the current row is being evaluated. It seems I have to use the UD02 dataview on the left.
#trans.dataView(‘UD02’).dataRow(trans.dataView(‘UD02’).row)[‘UPOrder_c’]# > 0 AND UD02.Key2 = ‘HP’
I would also like to try using the grid property on the left but haven’t got that to work either.
Anyways, back to what I actually have.
I have this and it evaluates to false as it should. I took out Key3 and it got results in the temp dataview of multiple records as it should.
UD02.Key1 = ‘#trans.dataView(‘UD02’).dataRow(trans.dataView(‘UD02’).row)[‘Key1’]#’ AND UD02.Key2 = ‘#trans.dataView(‘UD02’).dataRow(trans.dataView(‘UD02’).row)[‘Key2’]#’ AND UD02.Key3 = ‘#trans.dataView(‘UD02’).dataRow(trans.dataView(‘UD02’).row)[‘Key3’]#’
Here is the event.
Thing is, the dataview-condition widget acts as though it were successful and continues processing. It should not process at the point of testing where I’m initiating this event.
There is no data in the temp dataview for any found rows, so why is it firing the event as if there was a single match?
The reason for this functionality is because there are records that are hidden in the grid, but when you load a part initially the current row of the UD table is not any of the rows displayed in the grid.