Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Saturday, November 05, 2005

Tricky Issue with reports

This post is related to the previous one. I ran into this problem right after I was able to resolve the issue below.

So I am back to consolidating the reports for them, which would allow the Order Entry people to do what they call "Batch Confirmation". So they entered in about 10 orders, verified them, and then went to the Sales Update > Confirmation dialog, entered their selection, and brought up the 10 sales orders to 'Batch' confirm them. This process would turn the now qoutes into actual sales orders, and also print out all associated paperwork.

Well we ran into another issue here, were our 'work order' report will display an image that it gets from the network. Well this works fine when ran from the context of the 'client', but now since the report is called from the SalesFormLetter_Confirm.run() {...} method it has to run from the Server context. The fix to this was easy though, because when I walked through the code, I saw where when the report was designed a WinApi::FileExists() {...} was being done. This was returning true when ran from the Cleint context, but false when ran from the Server context.

Reason of course, as I am sure the flags have went up in your head by now, is because of a security issue. The AOS server, service was set to run under a local system account. We had to change this to a network account that had all the needed rights for the AOS to run correctly, and also access the images on the network. Once this was changed and the AOS restarted, the report worked liked a champ!

Find a job at: www.DynamicsAXJobs.com


Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved