By using this website, you agree to our Terms of Use (click here)
Hello all,
Somewhat off the cuff question. I am hiring for a new position in my company and one of the responsibilities will be to help the ongoing implementation of ACU and more pointedly around developing more reporting/dashboard capabilities. I have been able to fuddle my way through my most basic needs.
But my question is someone with strong SQL coding skills a real benefit with ACU GI and report creations?
I am trying to evaluate how much of a strength in depth knowledge of SQL would be to report building and GI creation.
From my perspective as a SQL developer, I often get frustrated when working with Generic Inquiries and Report Designer because what would normally be easy in SQL requires you to jump through hoops in Acumatica if what you are trying to accomplish can even be done.
My strength in depth of SQL knowledge has helped me design some work arounds to get the results I needed. I have had to read the SQL generated by Acumatica and try different approaches in the generic inquiry and report builder environments to achieve the desired results.
I think the more experience one has with different building tools and data access methodologies the better.
This forum is full of clever techniques used by some very talented individuals, therefore being able to check your ego at the door and not be afraid of asking basic questions is a plus. I have found it much faster to ask if someone has already solved a particular issue than spending a lot of time reading the SQL code generated by Acumatica. While you may not get an exact match all the time you will find techniques used by others that you can adapt.
Sometimes it is as easy but not as intuitive as using a different DAC or just adding one more DAC.
In my opinion, at the end of the day, you want someone who has great understanding of business and accounting concepts with experience using a variety of report writing tools and not afraid to ask basic questions.
I agree with Patrick.
Also, I personally find that my SQL knowledge is very helpful when creating reports in Acumatica. I'm just not sure whether it needs to be a "requirement" or just a "nice to have".