Making a field required on a scrolling window

I learned something today. This issue came from the Dynamics GP Community Forum. A poster was using Modifier to try and make the Posting Description field in the lower scrolling window of the Analysis Posting Detail screen  a required field. She did everything right. Changed the field property to Required, modified the Alternate/Modified Forms and Report information and restarted Dynamics GP. Still, the 'Required' property was not being enforced. What's up?
What was up is that Dynamics didn't check that row to make sure all required fields were completed. It doesn't have to check because none of fields are required by Dynamics GP out of the box. So, if you're trying to make a scrolling window field required and it doesn't seem to work, make sure there is at least one required field on the scrolling line.
Enjoy!
Leslie

Quick and Dirty Checklist for Modifying Word Templates

I was asked recently for the basic steps on how to modify Word templates. They didn't need step-by-step instructions, just something to help them along the way. Here's the list I came up with. I'm sure something is missing; I trust you will correct me where I'm wrong. As I told my colleague, this is the best I could do waiting for the train.

Modifying Word Templates can be kind of tricky. I've accumulated the steps and put them together in a list. Of course, before you try any of this you should back up your database, your existing Word templates as well as your Reports dictionaries.

1. Modify the Report Writer report such that it is properly printing (without errors) the values you are wanting to print on your Word template. Be careful of what section you place your new fields, it matters. If the Report Writer report doesn't print clean, you can't move on and expect to succeed.

2. Change your Alternate/Modified Forms & Reports ID so that you are pointing to your modified report.

3. Print your modified report. In the report destination window, there is a field 'What Type'. Here you select the option between Template and Standard. Choose standard, don't hit OK yet.

4. In the Destination Area, check both Screen and File.

5. Browse to a place you want to save your file, say the desktop, and change the file format to .XML

6. The Report Writer work is done, now you have to address your Word Template. I'm going to presume you have templates turned on and you have the template we're modifying set up as the default template for your company.

7. Open the Template Maintenance window and find the template you want to modify.

8. Once you have it in the window, click the Modify button at the top of the window.

9. Word will open to a layout version of your report. Save this on your desktop.

10. Click on the Developer Tab in Word's ribbon bar/tool bar.

11. If you do not have a Developer tab, turn it on using Word Options.

12. Over to the far right you'll see the Dynamics logo - the colorful one, click it. It says field list under it. If you do not have the Dynamics logo button, install the Word Addin from the GP install media.

13. When you click on Field List, a pane opens up on the left side of the window. At the top of that pane is XML Resource

14. Click on the down-pointing chevron and select SOP Blank Order Form.

15. Back to the Developer Section, select Remove Source. Accept the warning.

16. With the old source gone, now you need to add a new source.

17. Click on Add Source and select that XML file you created from Report Writer.

18. Put the new fields on your template and make any other changes you want.

19. Save the Word Document to your desktop and don't forget its name.

20. Close Word.

21. Go back to GP and open the Report Template Maintenance window if it isn't already open.

23. Select the Template Name of the report you modified and click on the green plus sign near the top.

24. Select the Word Document you just saved after your modifications.

25. Click OK when it tells you you've already got a template with this name.

25. Double-check your assignments and print your newly modified report.

Live the Dream!
Leslie

The Customer is its own Parent

Recently I've read some posts regarding National Accounts. There are a few items I wanted to note.

1. Once you have posted a transaction between the parent and the child - the child cannot gain independence again, nor can it run off to a different parent.
2. On the Customer Card, the parent needs to have itself as its Parent Customer ID - making them a parent in the National Accounts Maintenance window will automatically accomplish this. If you import the children into the National Accounts master - don't forget this detail.
3. If the children are all removed from the parent, the parent will still have itself as its own parent.
4. If you want the former parent to become a child of another customer, you will not be able to do it until you take away its Corporate Customer ID (which is its own ID)
5. The only way I know of to fix the former parent problem, is to use SQL and remove the record from the RM00105 table (the RM National Accounts Master)

Moments after I posted the above, I received a note from Brenner Klenzman at WilloWare Software  about a neat customization you can get from them. Here's his story:

 

" As an ISV, a VAR is a National Account for us [Willoware], with their Customers (end users) being the children in the National Account.

However, there is often more than one VAR/partner involved with a single customer.  So one customization allows us to assign any VAR as the “parent” on any given invoice.  Essentially there is a Primary Parent, and an unlimited number of Secondary Parents.

Also, since customers often change VARs, another customization allows changing the Primary Parent (i.e. the National Accounts Parent)."

I hope this helps someone who may be struggling with National Accounts.

Live the dream!

Leslie

 



VKonnact - a Fresh Look at Data Integration

I recently looked at a relatively new product on the market for integrating data into Dynamics GP. It's called VKonnact and it uses eConnect for the backend but shields the user from all of the eConnect complexities. While I haven't finished my review yet, what I've seen so far is very interesting. It's more user friendly than other products in the channel and has a user interface that looks nearly identical to the GP windows you are used to seeing. If you are thinking about purchasing an integration solution, definitely give this one a look. More to follow once I finish my review.
Live the dream!
Leslie

~internal~ Windows have no place in security

Have you ever wanted to use security to disallow the system Setup Checklist? You access this window using the Microsoft Dynamics GP button and then Tools > Setup > Setup Checklist. As it turns out, you cannot turn it off. Any window resource that has the name ~internal~ is not available to the security model. Now, if you hacked the dictionary (NOT recommended and a violation of your license agreement) and changed the object's name, you could then get to it, but that's not a good idea.

I had a bright idea once and thought I could use Modifier to move all of the fields off of the window. That worked fine, except it wasn't available to select in the Alternate/Modified Forms and Reports window (such a catchy name). I read a GPUG forum post from Jeff Martin that said you could include the Setup Checklist window in a VBA project, so I set out to see if I could get it to work with VBA. Sure enough, you can cause the window to open invisibly, but that doesn't really solve the problem. The reason for this post is to publish a tidbit revealed to us by David Musgrave of Winthrop Development. He said that "part of the issue with the checklists window is that the one window is used for all checklists from all series". I did not know that. Another mystery solved. Thank you David.

Live the dream!
Leslie