I looked at the class source code you mention briefly and noticed something curious. There is a partial class defined in the class file for RefreshRate that includes a class header comment referencing: “RefreshCurrencyRates.RefreshRates(RefreshFilter, List{RefreshRate}, string)”Notice the third parameter. Is this an incorrect header comment, or is there a third parameter hidden from us somehow? I don’t know the answer. In any case, two things I would suggest to try are (1) in your PXOverride method, call Base.RefreshRates() instead of the delegate method. However, I’m not quite sure if that would cause an endless loop if calling the Base would then call the PXOverride method again. (2) Don’t PXOverride the method, but instead add an event handler for RefreshFilter_RowSelected that calls your new method instead of the base version of RefreshRates().
If I understand correctly, you created a new action and want it to display an error like the existing MemoCheck() method does that you reference. Do you want to call the same MemoCheck() method from your new action? If so, you can simply instantiate the SOOrderItemAvailabilityExtension graph and call the method. If this isn’t what you’re trying to do, please explain further.
I’m not clear on what you’re trying to accomplish. You mention MemoCheck() “doesn’t seem to be working”. What specifically is not working?
@Ahmed That is an interesting alternative. I suppose that would work if you don’t mind the content living in the project.xml file of the package instead of a dedicated README-style text file.
@Django, the second extends the base. Are you going to suggest that I extend the first one instead? That’s a good idea, but I wonder if the UI controls will still need duplicated. I’ll give this a try.
The tab is still duplicating on the screen unfortunately.
@Django, I had that thought, too, but the IDs are all the same on both tabs.
I ran across this post when trying to resolve this issue for an instance myself. The only way I was able to resolve it was to rebuild the instance unfortunately. So apparently this is still an issue in 23R2. I’m guessing there’s some embedded code in the db somewhere that won’t clean up itself when all of the fields and all referenced code has been updated with the renamed fields.
Please supply sample JSON that doesn’t seem to be working.
@Chris Hackett Have not resolved yet, no. Will probably get back to this and look for some kind of workaround soon.
Thanks @andriikravetskyi35 ! That made it work.
Instead of redeclaring the view in graph extension 2, I tried instead to add the joins in the graph extension 2 Initialize(): Base1.CFPPKItemReqs.Join< LeftJoin<InventoryItem, On<CFPPKPMItemReq.inventoryID, Equal<InventoryItem.inventoryID>>, LeftJoin<INItemClass, On<InventoryItem.itemClassID, Equal<INItemClass.itemClassID>>>>>();Same bad behavior on link click.
@bcameron , Sorry, I can’t remember exactly, and can’t find that case (I don’t think I have access to it since I changed companies recently).
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.