Search Dynamics GP Blog. Subscribe. Enter your E-mail address in the box below and subscribe to our blog feed. Subscribe in a reader ¬∑ ‚Üź 7/30: Accounts Receivable Month-end Procedures in Dynamics GP ¬∑ What Are The¬†…
See original article:
Support Debugging Tool – Finding Tables that make up Windows …
July 23, 2013
¬∑ tidestone ¬∑ No Comments
Tags: 04101-207-761-2133, 3rd-floor, accordion, collapsible, cookie, dynamics, rights, rights-reserved, solutions, tidestone-solutions, type, var-collapsible ¬∑ Posted in: Blogs I Follow Total Views: 237
We recently released a new set of templates for Extender and SmartList Builder to use with Microsoft Dynamics GP 2013. I wanted to outline for you what they are and why I think they are a great resource for everyone to use.
SQL Server Reporting Services 2008 R2 introduced many features in the area of graphical display of information. According to MSDN, there were three new features introduced in SQL Server 2008 R2‚ÄĒmaps, sparklines and data bars and indicators. This final article of a three-part series on data visualization will explore the features of indicators as we build reports using Dynamics GP data.
Setting the Stage
Indicators are a way of providing immediate visual clues about the status of something. For example, while bar charts are a nice way to compare things to each other, sometimes you want to know the status of things right now so you can take immediate action. Are sales up or down right now? Is there an inventory shortage? By using indicators, you can provide those immediate clues to users that allow them to see the status and then look at the details.
According to Microsoft‚Äôs TechNet website, here are four benefits of indicators:
- Trends by using trending-up, flat (no change) or trending-down arrows
- State by using commonly recognized symbols, such as checkmarks and exclamation marks
- Conditions by using commonly recognized shapes, such as traffic lights and signs
- Ratings by using commonly recognized shapes and symbols that show progress, such as number of quadrants in a square and stars
In this example, let‚Äôs build a report that provides indicators based on how much of each item we are selling. The report is going to be grouped by customer class and item class.
First, once we launch Report Builder, we‚Äôll create a data source.
Second, we create a dataset. Here is the query for the dataset.
Once the dataset is created, we will use the toolbar in Report Builder to insert a matrix.
The next step is to add a column where the indicator will be placed.
Click in the matrix and then highlight the Extended Price column. Right-click and choose ‚ÄúInsert Column,‚ÄĚ then ‚ÄúRight.‚ÄĚ
From the toolbar, click ‚ÄúIndicator.‚ÄĚ
Click the new column in the Item Description row.
A window showing indicators appears. In our case, we‚Äôre selecting the five-star indicator in the Ratings group.
Once you have placed the indicator in the matrix, right-click on it and choose ‚ÄúIndicator Properties.‚ÄĚ
Click on ‚ÄúValues and States.‚ÄĚ
Enter the ranges that will determine which star will appear. You will see that there are various options for customizing the indicator on this window.
Enter the values and click ‚ÄúOK.‚ÄĚ
Here‚Äôs how the report appears in Design mode.
Click the ‚ÄúRun‚ÄĚ button to view the report.
Expand the report to view details by Item Description. Notice the varying amount of colors in the stars based on the sales value.
As you can see, the report indicates (Notice how I used the word?) the Cantata FaxPhone 9800 is doing well, whereas the Shoulder Rest ‚Äď Deluxe White is not.
This article just scratches the surface of adding some visualizations using indicators to your SSRS reports. In just a few steps, you can add these visual elements to your reports. Feel free to experiment using Report Builder or Visual Studio.
For more information, please contact our Microsoft Dynamics GP Support Center.
A few days ago, Errol Schoenfish on the Inside Microsoft Dynamics GP blog announced the forthcoming Microsoft Dynamics GP 2013 SP2 (or H2 as he named it) for Q4 of the 2013 calendar year. The part of the announcement which ‚Ä¶ Continue reading ‚Üí
Follow this link:
Microsoft Dynamics GP 2013 SP2 Announced for Q4
July 23, 2013
¬∑ Ian Grieve ¬∑ No Comments
Tags: business analyzer, Dexterity, internet, manufacturing, microsoft, microsoft-dynamics, project-accounting, Smartlist ¬∑ Posted in: Blogs I Follow Total Views: 356
Let’s jump right in. We debug our Visual Studio applications over and over; and attaching to the test environment is among the most important, and time-consuming skills we use. (How many times have I launched GP2010 when I was thinking of GP2013?)
Of course we all simplify our testing by building the dll and pdb files directly in the DynamicsAddins folder (right?). If not, start doing that.
Were that the only thing to learn here, that knowledge alone would be worth the price of admission. But it’s a fairly obvious step, and many of us already send the built dll file to the folder.
The next level is launching and properly attaching to the right Dynamics process‚Ä¶automatically.
A huge shout-out to Patrick Roth for showing me this.
First, verify you are automatically building to the DynamicsAddins folder. Otherwise the real value of this blog is blunted quite a bit.
- Within Visual Studios, Solution Explorer, select the project you are working on.
- Click on the Project menu, and click ‘project name Properties‚Ä¶’
- C-Sharp:Select the Build tab, and change Output path to your DynamicsAddins folder.
- VisualBasic: Select the Compile tab, and change the ‘Build output path:’ to your DynamicsAddins folder.
With that sorted out, we can now simplify the Debug process.
Second, in the same Properties window as the First step above, select the Debug tab ‚Äď this tab is the same for both C-Sharp and VisualBasic.
- Change the ‘Start Action‘ radio group to ‘Start external program:’
- Click on the ‘‚Ä¶’ button, and select Dynamics.exe within your Dynamics folder.
- Your project now knows to launch Dynamics.
- Be sure the text box contains entire path as well as the file.
- Under ‘Start Options‘:
- Change the ‘Command line arguments:‘ text box;
- Enter ‘DYNAMICS.SET’
- If you have a more-preferable SET file, for testing or other reasons, enter that SET file instead.
- Change ‘Working directory‘ to be the path where the SET file is located.
- Generally, it’s the same as the ‘Start external program’, but without the Dynamics.exe.
- Be sure it ends with ‘/’.
- Save the project.
Finally, as needed:
- Build the file (F6), which automatically is built in the DynamicsAddins folder
- Alternatively, build and copy the dll and pdb files to the DynamicsAddins folder
- This is useful if Visual Studio doesn’t have rights to the Dynamics folder.
- Debug (F5).
Once it’s set up properly, clicking on F5 should launch Dynamics for you. Behind the scenes, your code is automatically ‘attached’ to this instance of Dynamics.exe.
To fully see the power of this, place a ‘Toggle Breakpoint’ (F9) on the first line in your code’s Initialize() method. Then click ‘Start Debugging’ (F5). The code should automatically break on that line after launching Dynamics. (Try doing that by ‘Attaching To Process‚Ä¶’)
Plus, once this is set up, I no longer launch GP2010 when I meant to launch GP2013 ‚Äď except for the first time after an upgrade :-).
See more here:
Debugging Visual Studio Tools Tips
July 23, 2013
¬∑ LeeRB ¬∑ No Comments
Tags: Customizations, developer toolkit, Dex.ini, extender, featured, integration, lee butenhoff, security, Smartlist Builder, upgrade, visual studio tools, windows ¬∑ Posted in: Blogs I Follow Total Views: 339
Part 3 – Resolving Microsoft Dynamics GP 2013 Web Client Functional Issues
Last week, Part 2 of this series dealt with resolving Web Client implementation issues. The key to remember is any exception condition prior to the Microsoft Dynamics GP login window is treated as an implementation issue and as noted back in Part 2, there are two major processes – steps, if you will – in compiling information that will lead to resolving Web Client exceptions.
Just like with the implementation issues, you must compile information related to all application exceptions.
Let’s see what type of information can be compiled:
- If the problem involves product functionality, it’s always a good idea to record the steps to reproduce the problem.
- It’s also possible that the issues are UI related, i.e., a window does not display correctly (though these issues are less frequent, but certainly possible).
- Printing and data export issues. In this case, you will want to determine whether the Silverlight application is being trusted.
- Silverlight exceptions, i.e., those displayed in a window with a stop sign
- Third party application customization vs. standard Microsoft Dynamics GP functionality. In a multi-dictionary setting, this will play a role whether using Web Client or the Rich Client (traditional Dexterity application).
- Enable all available Web Client logs (session management and multi-tenant logs)
- Capture all user-machine related information with MSINFO32.EXE
- Can you reproduce the problem in the standard Microsoft Dynamics GP rich client application
- Can the problem be reproduced by more than one user
- Can the problem be reproduced in more than one company
The following¬†are sample application exceptions:
|App stuck on “Initializing” upon login|
As you can tell, some of the information that must be compiled is standard. What must be taken into account here is, the Session Service is a real GP client running in the background supporting the Web Client session.
With that said, the following are some key success factors for the resolution of Web Client functional issues:
- First, all issues must be treated jointly as Microsoft Dynamics GP issues and not something isolated to the Web Client.
- You must keep in mind that Web Client will display the same exception messages displayed by the standard Microsoft Dynamics GP rich client.
- Breakdown the problem and make sure it’s focused on the Web Client.
- The Web Client functionality “resembles” that of the Microsoft Dynamics GP rich client – we use the word “resemble” here, because we know certain things like navigation are slightly different in Web Client.
- The rich client is installed on the Session Host server(s), therefore files like DYNAMICS.SET, DEX.INI, and forms and reports dictionaries are still in the mix
- All exceptions experienced by the rich client are submitted to the Web Client, whether handled or unhandled.
- All Dexterity third party applications are supported in the Web Client.
- The Web Client uses a proprietary messaging system.
In part 4 of this series, I will look into some tools available for troubleshooting both implementation¬†and functional issues.
Until next post!
Mariano Gomez, MVP
View original post here:
Troubleshooting the Microsoft Dynamics GP 2013 Web Client – Part 3
July 22, 2013
¬∑ Mariano Gomez ¬∑ No Comments
Tags: Analytical Accounting, bank reconciliation, business, calendar, Dex.ini, General Ledger, management, middle-east, Multicurrency, support debugging tool, united-states ¬∑ Posted in: Blogs I Follow Total Views: 348
I don‚Äôt often re-post things from other blogs, but this is just too good not to share. David Musgrave recently published an update to his spSearchOnAllDB stored procedure¬†on his blog, Developing for Dynamics GP.
Simply run the script to create the stored procedure and you can search all the tables in a database for a particular string or value. You might not need this frequently, but when you do ‚Äď what an incredibly powerful tool to have.
Check out David‚Äôs post to download the script and see notes about usage. Thanks David!
You can see links to other helpful SQL Server tips on my SQL Server Coding Tips page.
Read this article:
SQL stored procedure to search an entire database
July 22, 2013
¬∑ Victoria Yudin ¬∑ No Comments
Tags: archives, dynamics, events, featured, Inventory, mariano-gomez, miscellaneous, reports-viewer, sql server, victoria-yudin ¬∑ Posted in: Blogs I Follow Total Views: 487