You’re offline. This is a read only version of the page.
2,281
I've done several Project Accounting integrations using eConnect and .NET, and I've done a few PA customizations using Modifier, VBA, and Visual Studio Tools.
Based on those projects, my assessment is that those tools have about 90% of the functionality required. For instance, eConnect schemas are missing some required fields that I have to handle with custom code. And VS Tools APIs lack access to certain GP objects or functions.
I'm wondering if anyone has done a PA customization using Dex, and if Dex seems to have a more "complete" API for PA.
I am inquiring because a client is asking for a PA customization, so I'm looking to see if Dex would be a more suitable tool than Modifier/VBA or .NET.
Thanks,
Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified Professional
*This post is locked for comments
Hi,
This mean that i cannot create a custom workflow for the PA Contract Maintenence? This require to modify this widows in dexterity.
Sorry for my english.
Thanks,
Edve
Hello, Steve. I have been doing Dexterity development for 12 years, and have done a lot of customizations against Project Accounting (PA) using Dexterity and Modifier/VBA, as well as integrating to PA using eConnect.
I'm curious to get more details about the specific shortcomings you're experiencing. Dexterity is definutely the most powerful development tools for GP, but it has a number of limitations when it comes to interacting with any 3rd party dictionary, which Project Accounting basically is (yes, I know it's offered by Microsoft, but it's not part of the core GP dictionary. Therefore, it basically acts and must be treated as any other 3rd party product).
The first and biggest shortcoming is that Dexterity cannot be used to modify a PA window. That is, we cannot add new fields to a PA window. The only way to add new fields to a PA window would be with Modifier/VBA. If we were dealing with a core window like the Sales Transaction Entry window, the Dexterity could be used to add to the window.
The second big struggle with using Dexterity with any 3rd party product like PA is that it can be really complicated to do what is called "cross-dictionary" development. Debugging takes longer, and so does interaction. However, it is still way easier than Modifier/VBA to interact with Project Accounting functionality. For instance, I once had to default special tax schedules at the time of billing into the Project Billing Entry window, ensuring of course that taxes were in fact calculated using the schedules I specified. Try doing that with Modifier/VBA... YIKES! But with Dexterity, I was able to intercept the PA function for getting the tax schedules, was able to specify my own, and BAM! It worked great.
As for integration, yeah, I've been a little frustrated that there are not more options for eConnect and PA. For instance, there are eConnect objects for building contracts, projects, and budget details, but no eConnect method for creating the Project Budget IV Details. I once had to do that, and wrote my own custom eConnect method for it. Also, there is no interface for creating Billing transactions. That's on my wish list for the future.
So, there are pros and cons to choosing the different development and integration tools. If you like, post or email me with more details, and I'll offer some pros/cons specific to your situation.
Good luck!
Ron Draganowski
Manager, Technology Services
RSM McGladrey, Inc.
Minneapolis/Saint Paul, Minnesota
ron.draganowski@mcgladrey.com
Find me on LinkedIn: http://www.linkedin.com/in/rondraganowski
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (