RightClick-Details in Dataview: How does it work?

I've modified a Property in an existing Dataview (A/P Aging Report) in order to change its datatype (LongInteger/Int64 to String) to fix a bug.
Modification done through IDO Extend&Replace.
The dataview displays fine, the bug is fixed.
However when I right-click in the Dataview on this modified property (Voucher property, now called LIO_Voucher), then click Details, it still opens the relevant form (A/P Posted Transaction Detail) but instead of filtering data on the selected Voucher value, it stops with a popup error message "Invalid column name 'LIO_Voucher'."

I've check the Property Class of both Voucher/LIO_Voucher properties and they share the same values; the only difference is the datatype (and of course the property name).

How can I make this "RightClick-Details" work properly?

Find more posts tagged with

Accepted answers

Legacy Contributor

The answer is that it is driven by a Property Class and everything - formatting, right-click functionality, linkage to parent record data, is all driven by that Property Class. By changing/using a different property, you broke all that. On the property you created, you would have to create a Property Class Extension that restores all that functionality, by copying all the settings manually from the vendor default Property Class.

All comments

Caitlin Porter

Did you update the A/P Posted Transaction Detail form with the new property? It looks like the right click menu is working as it should, I believe the problem is related to that form not having the correct property on it.

Legacy Contributor

Thanks for the answer Caitlin, I really appreciate having someone from Infor helping us here.

I did not change anything in the A/P Posted Transaction Detail form because it's not the same IDO and the bug in the Dataview's IDO is not there in the form.
You're suggesting that I rename the form's property like I did for the Dataview property, without changing anything else than the property name? It seems to me overkill/dirty to have to propagate such change in waterfall into other forms and IDOs when I'm actually just adapting an ill-designed property type that's not matched to the values returned by its own SP.
From your answer, I'm guessing that the "RightClick-Details" is trying to match properties by exact name... is that really it? Any other way to tell the Details function to take the "right" property name in the form?

Legacy Contributor

Ok thanks, that makes sense, so I need to extend my custom property's Property Class too. I'll try that.

Legacy Contributor

Can you confirm what version you are working with? In CSI 10, Accounts Payable Aging Report is a Form report, not a DataView, so sounds like you are working with a custom object, which could be part of your original issue.

Legacy Contributor

9.01.01 on-prem, the Accounts Payable Aging Report *Dataview* has been provided by Infor Support, telling me it should have been there OOTB and they didn't know why it wasn't. I just had to import the dataview with its input parameters, and modify the Preview button's Event Handler to add the link to the dataview passing the form's report parameters.

Legacy Contributor

Hmm, yeah that is not correct. Checked multiple CSI instances and none have that DataView. They may have created it for another customer, but it isn't a standard DataView and I can't vouch for its functionality.

That said, that really isn't your issue. Below is a screenshot of the Property Class Extension dialog for VendNum:

The screenshot shows where the right-click menu would be specified. Other than specifying that you want it to use the StdDetailsAddFind right-click menu, you can't really control how the StdDetailsAddFind works. So unless you are using the actual VendNum field, it won't be able to link to the appropriate records and forms.

If it was a regular form, you could override the functionality by creating a Form Event for StdCurCompDetails and specifying actions to perform when that fires, such as opening a form filtered based on your custom value.

Legacy Contributor

Ok thanks, actually with the screenshot I understand that I didn't know about actual "Property Class Extensions"... What I did is just to create a new Property Class by copying the original one and modifying it (like an IDO). In the end I managed to make it work with this only: in the Dataview Actions Setup I added the Class Name and now it works fine with my new Action entry! (previously I forgot to Check In my new Property Class and to do Ctrl+U).

Copyright © 2025 Infor. All rights reserved.