By using this website, you agree to our Terms of Use (click here)
Not really sure how explaining this to you will solve my problem, but in a nutshell, we need to have a filter on Bills to filter out our conversion data which has a different prefix to our data since go-live. Now that filter is being applied to payments as well. So I fixed the Bills issue but now it's created an issue for Payments. The filter is defined as default so that when all users open Bills, they see non-conversion data. But when they open payments, they have to change the filter.
It's stupid and makes no sense.
Edit: in writing this down i came up with a solution - I've changed my filter to be date based and using the go-live date as the cutoff, all conversion data is now filtered and checks and payments data is displaying as expected with the same filter.
I don't know Royce, I think Juriy might know what he's talking about here 🙂
@juriy-zaletsky, I can't access the site. Were you able to solve the problem using a Customization Project?
Yes, I solved the issue with help of customization. Please try to check again and see ( I had to restart that server due to updates ).
The issue isn’t solved, it remains the way it is in the base product. Customising to address base product issues doesn’t solve anything. The issue is trying to get Acumatica to understand the design flaw here but that doesn’t appear to be happening. Anyway we will survive with my workaround.
Ugh, I failed to go to the second page of this thread. That's why my last reply didn't make a lot of sense in the context of this second page. Second time I've done that. Gotta be more careful. My bad.
I agree Royce. It would be nice to get it fixed in the base product. Sure seems like the Acumatica application is trying to be "too smart" here.
But I definitely appreciate Juriy's effort to come up with something.
Online Members
