Page 1 of 11412345678910...2025303540...Last »

Microsoft Dynamics GP 2015 not showing Service Enabled Procedures

David Meego - Click for blog homepageIt has been a while since I last posted on the blog. I have been working flat out to finalize the GP Power Tools code and documentation. All I can say is that the Microsoft Dynamics GP community will be amazed with some of the new features and will love the improvements above and beyond the Support Debugging Tool. I will be starting a “What’s New” in GP Power Tools series of posts soon.

Anyhow, the subject of today’s post is an issue in Microsoft Dynamics GP 2015 that I discovered while testing the GP Power Tools code.

The Security Task Entry window can be used to add access rights for Service Enabled Procedures in any of the product dictionaries.  Just select the Security Task ID and then select the product, Type as Service Enabled Procedures and the series.

SecurityTaskEntry2Security Task Entry working

All seems working as expected…. until you create a modified forms dictionary for that product, by going into the Modifier. You don’t have to make any changes, the existence of the forms dictionary is all that is needed. Now the Service Enabled Procedures for that product no longer show up.

SecurityTaskEntry1
Security Task Entry no longer showing Service Enabled Procedures

As I have very similar code in the new Script Explorer window in GP Power Tools, I was seeing the same behaviour. This is what sparked the investigation into what was happening.

I tested the code that reads the dictionary and it is able to see the list of global procedures in the dictionary fine, but the check to see if the script is Service Enabled with the Script_GetSystemProperty() function fails to return the any data and so no scripts can be identified as Service Enabled.

I have reported this issue to Microsoft.  In the meantime, if you need to set security to Service Enabled Procedures, temporarily rename the custom forms dictionaries and re-launch Microsoft Dynamics GP.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2015, Dynamics, GP, Microsoft Tagged: Application, Exception, GP 2015

Read more here:
Microsoft Dynamics GP 2015 not showing Service Enabled Procedures

June 30, 2015 · WinthropDC · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 10

Welcome to the first GPUG Chapter outside of North America

David Meego - Click for blog homepagegpug-logo

I have been involved in GPUG (Dynamics GP User Group) over the few last years, primarily because I was presenting at conferences in the US which GPUG was organising or at least had a presence at.

As I learnt more about what GPUG does for the community, I realised that I wanted to bring the benefits of an organised user group to my home town in Perth.

So, after promising Kim “Mama” Peterson for a long time that I would start a Perth chapter of GPUG, I finally bit the bullet and booked a room at the local Microsoft Office and began planning our first meeting.

Last Wednesday night we had our first meeting with eleven attendees. We had representatives from four customer companies and two of the three local partners (the third partner gave their apologies and promised to be at the next meeting).

GPUGPerth

Before the meeting got started, we had some social time to chat and eat pizza. Free food… always a great reason to attend. :-)

My long time friend (and SQL Guru) Robert Cavill from Emeco presented a member showcase. It was the best member showcase we had ever seen (also the only one), but it should be the first of many.

I also gave a demonstration of the upcoming GP Power Tools product, showing how to use it to resolve a variety of security related issues. The demo included some of the features from its predecessor (the Support Debugging Tool), but also included some functionality newly added to GP Power Tools.

Thanks to Michelle, Katherine and Fiona from the Perth Microsoft office for their assistance and to Rose, Jennifer and Kim from GPUG for working with me to make this happen. Finally thanks to the local partners and customers who took the time out of busy schedules to come and attend.

The next meeting is scheduled for September. Exact details will be published later.

If you are a customer in Western Australia, we would love to see you at the next meeting.

David

PS: I found out that not only was this GPUG chapter meeting, the first in Australia, but also the first outside of North America.

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: GPUG, News Tagged: GPUG, News

Continue reading here:
Welcome to the first GPUG Chapter outside of North America

June 12, 2015 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 34

Microsoft Dynamics GP 2015 R2 now available

David Meego - Click for blog homepageThanks to a GPUG forum post from Lou Spevack, I found out that Microsoft Dynamics GP 2015 R2 has been released over the weekend.

The development team are delivering on the faster release schedule promised at the recent conferences.

The links for the downloads are below:

For the DVD image go to the following page:

For the Patch file go to the following page:

I have also created a new page on the blog with the links for all current versions:

Enjoy

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2015 R2, Dynamics, GP, Microsoft, News Tagged: Application, GP 2015, News

Link:
Microsoft Dynamics GP 2015 R2 now available

June 1, 2015 · WinthropDC · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 54

Microsoft Convergence Atlanta 2015 (#CONV15) – Wrap Up

Hey, not that this concerns anyone, but finally here is the wrap up post for the Convergence 2015 event. It’s really been a busy couple of seasons for this writer (not that I’m complaining!), so I have had to opt for work instead of blogging which I’m sure you will understand as a reader.

Microsoft Convergence Atlanta 2015: GPPC PreGame

Microsoft Convergence Atlanta 2015 (#CONV15) – Day 1

Microsoft Convergence Atlanta 2015 (#CONV15) – Day 1 Continued

Microsoft Convergence Atlanta 2015 (#CONV15) – Day 2

Microsoft Convergence Atlanta 2015 (#CONV15) – Day 3

Microsoft Convergence Atlanta 2015 (#CONV15) – Day 4

Other entries on the event, from my good friend David Musgrave:

#CONV15 – Convergence 2015 Atlanta – Day 0 – PreGame

#CONV15 – Convergence 2015 Atlanta – Day 1 – Opening Keynote

#CONV15 – Convergence 2015 Atlanta – Day 1 – Dynamics GP Session

#CONV15 – Convergence 2015 Atlanta – Day 1 – Continued

#CONV15 – Convergence 2015 Atlanta – Day 2

#CONV15 – Convergence 2015 Atlanta – Day 3

#CONV15 – Convergence 2015 Atlanta – Day 4

#CONV15 – Convergence 2015 Atlanta – Post Conference and Getting Home

At the time of this writing, I’m preparing myself for the GPUG Summit conference in Reno, Nevada. Things are continuing to be hectic

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Read More:
Microsoft Convergence Atlanta 2015 (#CONV15) – Wrap Up

May 24, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 57

Friday Funny: Finally…. The correct way to eat Vegemite

David Meego - Click for blog homepageIn recent years when I have come to conferences in the US, I have been bringing a stash of goodies with me.

Usually, this includes Arnott’s Tim Tams and Allen’s Chicos*, which are liked by almost everyone who tries them. And then there is the Aussie Icon, Vegemite.

The reaction I get from most people is one of abject terror, completely horrified when I suggest they try some vegemite. They will tell me how they have seen other Americans try it and that it is horrible, disgusting and compared to vomit.

US TV Hosts try Vegemite for the first time live on-air to celebrate Australia Day (direct link)

 

The problem is that those people who have tried it (including celebrities and TV show hosts) usually have tried it wrong. Usually very wrong. To quote one of my favourite TV comedies:

Wrong, wrong, brimming over with wrongability – Rimmer, Red Dwarf.

The problem is that Vegemite is very (read VERY) concentrated. Imagine an extremely salty beef and vegetable stock boiled down to a thick paste. Would you eat a spoonful neat? You just can’t spread it thick like peanut butter or Nutella and expect it to taste anything but disgusting.

It was first made as a by-product from another Australian favourite, beer. It is a dark brown food paste made from leftover brewers’ yeast extract with various vegetable and spice additives developed by Cyril P. Callister in Melbourne, Victoria, in 1922.

Here is another reaction from a recent episode of Jimmy Fallon’s Tonight show:

Jimmy Fallon and Steve Higgins try Vegemite (direct link)

 

So, finally it takes a famous Australian actor (and X-Man) Hugh Jackman to show Jimmy how to really eat Vegemite:

Hugh Jackman Shows Jimmy How to Really Eat Vegemite (direct link)

 

Hint: The butter (not margarine) should melt into the hot toast and the vegemite should be spread extremely thinly. If you can’t see the surface of the bread, you have it spread too thick and need to scrape some off.

That little 150g (5oz) jar should last a good 5 to 10 years. You can ignore the use by date. It never goes off and does not need refrigeration.

Go find some Vegemite and enjoy.

David

* While Allen’s is a Nestle brand, it seems they are too embarrassed to include Chicos in the product list.

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Fun, Public Service Announcement Tagged: Friday Funny, Fun

View article:
Friday Funny: Finally…. The correct way to eat Vegemite

May 22, 2015 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 51

The future of the Support Debugging Tool

David Meego - Click for blog homepageSince leaving Microsoft in October last year, I have been asked many times about the future of the Support Debugging Tool.

So I wanted to let people know what is happening with the tool and what to expect.

As mentioned in my earlier post: Update: Where is the Support Debugging Tool for Microsoft Dynamics GP 2015?, I have an exclusive agreement in place with Microsoft which allows me to continue work on and release the tool. In that post I asked via a survey what the new name for the tool should be.

So, as it has become a pain to keep talking about “the rebranded and upgraded Support Debugging Tool”, I have decided to confirm that the new name will be

GP Power Tools

Thank-you to all who voted.

GP Power Tools will be initially released for the following Microsoft Dynamics GP versions:

  • v11.0: Microsoft Dynamics GP 2010
  • v12.0: Microsoft Dynamics GP 2013 and GP 2013 R2
  • v14.0: Microsoft Dynamics GP 2015

GP Power Tools will be available via an annual subscription for each customer site at the special introductory price of US$365.00. That’s a dollar a day, and every four years you will get a day for free.

Here is the cool bit… with GP Power Tools you will get:

  • Everything you love about the Support Debugging Tool
  • New simpler Navigation with menus and area page
  • Database Validation, to ensure that your upgrades work
  • Numerous enhancements and the odd bug fix
  • And lots more….

So for now continue to use the free Support Debugging Tool for Microsoft Dynamics GP 2010 and GP 2013 (inc. GP 2013 R2) available from http://winthropdc.com/SDT. Stay tuned for more information on when to upgrade to GP Power Tools for continued support and improved functionality.

Those of you on Microsoft Dynamics GP 2015 will need to be patient and wait for the release of GP Power Tools.

Watch this space (blog), especially the GP Power Tools Portal page at

Please post comments and feedback.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2010, 2013, 2013 R2, 2015, Dynamics, GP, GP Power Tools, Microsoft, News, Products, Support Debugging Tool Tagged: GP Power Tools, GPPT, SDT, Support Debugging Tool

See the original post:
The future of the Support Debugging Tool

May 20, 2015 · WinthropDC · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 64

Using the Support Debugging Tool to create user accessible SQL Scripts – Part 3

David Meego - Click for blog homepageThis is the third and final article in the series, make sure you look at the previous articles before this one.

The previous articles can be found at:

Today’s article adds the final step by adding a method for a user to execute the code we have written so far without requiring access to any Support Debugging Tool windows.

The Runtime Execute window and SQL Execute windows are Advanced Mode features which makes them only available to users with access to the Administrator features via the security roles AND the system password (if used) AND SQL dbo or SysAdmin privileges. You would not want this sort of access to be given to the average user, so you can use the method in this article to provide access to the scripts we have written from an existing window.

Using the Automatic Debugger Mode we can create a non-logging trigger to call our scripts when an event occurs in the system. The event used can be any of the system events supported by Dexterity, such as opening or closing a window, moving focus in to or out of a field (with or without changing to the field), or clicking on a button. You can also create your own items on the Additional menu to trigger off.

For our example, we are going to use two methods; an additional menu and re-purposing the window print button on the Customer Maintenance window.

Part 3: Exposing the script to any user

The final step is to use Automatic Debugger Mode Setup to call our previously created Runtime Execute script.

  1. Open the Support Debugging Tool main window (Microsoft Dynamics GP >> Tools >> Support Debugging Tool or Ctrl-D).
  2. Open the Support Debugging Tool Setup window (Options >> Setup Automatic Debugger Mode).
  3. Enter the Trigger ID, Trigger Description as desired for menu based trigger.
  4. Check the Start Trigger Automatically on Login, Do not activate Logging Mode and Minimize Debugger Log Entries checkboxes.
  5. Select the Trigger Type: Add Form Menu, Trigger Event: Form Level, and Trigger Attach: After Menu Selected.
  6. On the Resource tab, select Product Name: Microsoft Dynamics GP, Form Name: RM_Customer_Maintenance, Menu Entry: Check and Update Hold, Accelerator Key: U.
    Trigger1
  7. On the Script tab, set Context: Microsoft Dynamics GP and the script to:
    out boolean OUT_Condition;
    local text MBS_Text_Field;
    local integer MBS_Dictionary;
    local integer MBS_Status;
    
    OUT_Condition = false;
    
    if isopen(form RM_Customer_Maintenance) then
    	OUT_Condition = true;
    
    	call with name "MBS_Script_Load_Dex" in dictionary 5261,
    		"DEMO1", MBS_Text_Field, MBS_Dictionary;
    
    	call with name "MBS_Runtime_Execute" in dictionary 5261,
    		MBS_Text_Field, MBS_Dictionary, MBS_Status;
    	if MBS_Status <> OKAY then
    		warning MBS_Text_Field;
    	end if;
    
    end if;
    

    Trigger2

  8. You can use the Helper Button at the bottom of the window to insert Helper Functions at the current cursor location for loading and executing the Dexterity Runtime Execute script. Variables needed will be automatically added to the top of the script.
  9. No changes needed on the Actions and Options tabs
  10. Click Save.
  11. Enter the Trigger ID, Trigger Description as desired for button based trigger.
  12. Check the Start Trigger Automatically on Login, Do not activate Logging Mode and Minimize Debugger Log Entries checkboxes.
  13. Select the Trigger Type: Focus Event, Trigger Event: Field Change, and Trigger Attach: Before Original.
  14. On the Resource tab, select Product Name: Microsoft Dynamics GP, Form Name: RM_Customer_Maintenance, Window: RM_Customer_Maintenance, Field Name: WindowPrint.
    Trigger3
  15. On the Script tab, set Context: Microsoft Dynamics GP and the script to:
    in string IN_OldValue;
    in string IN_NewValue;
    out boolean OUT_Condition;
    
    local text MBS_Text_Field;
    local integer MBS_Dictionary;
    local integer MBS_Status;
    
    OUT_Condition = false;
    
    if isopen(form RM_Customer_Maintenance) then
    	OUT_Condition = true;
    
    	call with name "MBS_Script_Load_Dex" in dictionary 5261,
    		"DEMO1", MBS_Text_Field, MBS_Dictionary;
    
    	call with name "MBS_Runtime_Execute" in dictionary 5261,
    		MBS_Text_Field, MBS_Dictionary, MBS_Status;
    	if MBS_Status <> OKAY then
    		warning MBS_Text_Field;
    	end if;
    
    end if;
    

    Trigger4

  16. You can use the Helper Button at the bottom of the window to insert Helper Functions at the current cursor location for loading and executing the Dexterity Runtime Execute script. Variables needed will be automatically added to the top of the script.
  17. On the Actions tab, check the Issue Reject Script checkbox to prevent the original button script from running after our trigger code finishes.
  18. No changes needed on Options tab.
  19. Click Save.

To automatically enable the triggers, just log in again to the company. To manually enable the triggers, from the Support Debugging Tool main window, select Turn On Automatic Debugger Mode >> Non Logging Automatic Start Only. To disable the triggers, from the Support Debugging Too main window, select Options >> Automatic Debugger Mode Status and then click Unregister >> Non Logging Triggers Only. To disable all triggers, use Unregister >> All Triggers, this is required if you want to open the Setup Automatic Debugger Mode window again.

Notes

  • Use the Automatic Debugger Mode Status window (Options >> Automatic Debugger Mode Status) to confirm that the triggers are registered and active.
  • Note that the target window must be closed and re-opened after the triggers are enabled before they will be active.
  • If re-purposing an existing button, you can use an ask() dialog to ask if you want the original purpose or the new purpose to execute. For the original purpose, exit the script with the variable OUT_Condition equal to false. For the new purpose, perform the desired actions and exit the script with the variable OUT_Condition equal to true and the action Issue Reject Script ticked.
  • If you are having problems getting the code to work, uncheck the Minimize Debugger Log Entries checkbox to get more information recorded in the Debugger__.log file.
  • It is possible to load and execute the SQL Execute scripts directly using the Dexterity trigger code and bypass Step 2 of this series using Runtime Execute, however this makes it harder to test the code as you will need to keep registering and unregistering the trigger.

Below is the Debugger Settings files with all the code for the examples in this series.

Please write feedback and comments below to let me know how you think you could use these methods in your systems.

Hope you found this series useful.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Development, Dexterity, Dynamics, GP, Microsoft, Products, SQL Server, Support Debugging Tool Tagged: Application, Dexterity, SDT, SQL, Support Debugging Tool

Originally posted here:
Using the Support Debugging Tool to create user accessible SQL Scripts – Part 3

May 18, 2015 · WinthropDC · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 59