Saving a transaction using Visual Studio Tools for Microsoft Dynamics GP

(0) Share

Report

Posted on by Community Member

Hi,

I have a little Visual Studio 2008 dll that I made using the instructions that came with Visual Studio Tools for Microsoft Dynamics GP. It takes vales from a file and drops them on the Payables Transaction Entry screen in Dynamics GP. My problem is that I can't see how to save the transaction programatically so I can go onto the next transaction in the file ans so on. I am considering using the Continuum API CallVBAMacro method but this will involve setting up Modifier dictionaries in an environment where management don't want modifications or direct to table entries.

Does anyone know if there is a way to save a Payables Transaction Entry record (once it has been entered) using Visual Studio Tools for Microsoft Dynamics GP?

Many thanks.

Jim

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Richard Whaley 25,195 on at

Like (0)

Report
Copy link

Link copied!

It seems that you first have to reconcile whether you can write code or not. Can't have it both ways!

If your client does not want custom code, there are good reasons for it. If they want something you cannot obtain in standard code, try third party products, if it does not exist, then tell your client HIS/HER options: No function or custom code.

Then ask us....

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report
Copy link

Link copied!

[quote user="James McCulloch"]
Hi,

I have a little Visual Studio 2008 dll that I made using the instructions that came with Visual Studio Tools for Microsoft Dynamics GP. It takes vales from a file and drops them on the Payables Transaction Entry screen in Dynamics GP. My problem is that I can't see how to save the transaction programatically so I can go onto the next transaction in the file ans so on. I am considering using the Continuum API CallVBAMacro method but this will involve setting up Modifier dictionaries in an environment where management don't want modifications or direct to table entries.

Does anyone know if there is a way to save a Payables Transaction Entry record (once it has been entered) using Visual Studio Tools for Microsoft Dynamics GP?

Many thanks.

Jim

[/quote]

The right tool for the right job! If you are importing transactions from a file you are better off using a tool like Integration Manager or eConnect to get your transactions into GP. These tools can create a batch and save the transactions imported as needed.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Richard,

Thanks for your response. Code is fine. It is the direct table access, thereby bypassing anything GP might do to the transaction that they and I don't like.

Either the toolkit or the Continuum API let me programatically use the GP interface so there is no direct table entry and no bypassing of GP functionality. With a Modifier function I can wite a one line procedure that can press the save button and I can call the procedure with a 3 line procedure in the Visaul Studio project.

So everything is working just fine except that I can't believe there isn't a way to press the save button on a form using either Visual Studio Tools or the Continuum API. I was hoping someone would know the answer to this question.

Thanks again.

Jim

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Mariano,

Thanks for your reply.

There will be a number of data imports in this project and for some, the files with Vendor and Customer changes for example, where Integration manager probably won't do. Also I have used Integration Manager in the past for AP transaction imports and, while it works just fine, both the error trapping and the user interface seemed to cause problems. This could be just bias on my part.

I haven't looked into eConnect and maybe I should. Do you think I should spend the time on eConnect or just live with having to use all three of the Toolkit, the Continuum API and the Modifier to get what I want? Your opinion will be appreciated.

Regards,

Jim

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report
Copy link

Link copied!

Jim,

As someone said, "The best solution, is the one that works". With that said, I have built really complex data integrations with Integration Manager since the tool first came out in the market up to today. I can't see why you would need eConnect -- great tool by the way! -- for something as simple as importing a few payables transactions.

If you ask me, it is always good to know all tools possible, but be really good at a few.

Since you decided to go down the programmatic route with VST, here is the issue: you cannot really use any of the automation libraries provided with the .NET Framework (i.e., Windows.System.Automation) to drive certain Dexterity UI controls such as a button. In the ideal world you could even use a RaiseEvent to drive the button click event.

Nonetheless, you may be able to use the following code to drive the Save button.

// create a reference to the original vendor maintenance form

pmVendorOriginal = Dynamics.Forms.PmVendorMaintenance;

pmVendorOriginal.PmVendorMaintenance.SaveButton.Focus();
pmVendorOriginal.PmVendorMaintenance.SaveButton.RunValidate();

Good luck

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Mariano,

Thanks for your comments about eConnect. It does look goood but a lot of installation and learning curve what you correctly descibe as fairly simple (but high volume) imports.

I also agree with you about Integration Manager. However I think the addittional programatic control provided by the Toolkit in combination with the Continuum API and, as it turns out, a small amout of Modifier code will be of significant value in this circumstance.

The code you suggested was a good idea but, unfortunately, deletes the transaction and increments the voucher number without saving the transaction. The code might work for the Vendor card when I get there.

For now, I'm going to go with using the Modifier code. As you say, a good solution is one that works and this solution will appear very simple and elegant to the user. If I have a support request and time available in the budget, I may send in a support request on this issue and, if so, I will update you on the results.

Thanks again.

Jim

Was this reply helpful? Yes No