By using this website, you agree to our Terms of Use (click here)
Hi,
I am in the process of upgrading from 2019R2 to 2020R2 and having an issue getting @Me to work as expected on a GI using the CRActivity table. On Opportunities I am able to use CROpportunity.OwnerID = @Me and it works as expected. Using CRActivity.OwnerID = @Me, it filters out all records. I also tried joining BAccount and EPEmployee trying the BAccountID and UserID respectively but the result is the same... no data.
Anyone have an idea or am I doing something wrong?
Thanks,
Jeremy
For example, to use @Me on an Opportunity, I join the CREmployee table on CREmployee.DefContactId=CROpportunity.OwnerID and I am able to use @Me on the conditions or in the shared filters by referencing CREmployee.UserID (aka Employee Login). When I do the same join on CRActivity, it does not work. You can easily test by creating a GI with CRActivity and CREmployee, add CREmployee to the Results Grid, then create a filter where Employee Login=@Me.
I'm not exactly sure how the @me filter is affected by this, but I suspect that it has something to do with this change from uniqueIdentifier to int. See the few pages that start on the bottom of Page 32 of the Acumatica 2020 R2 Release Notes:
Online Members
