The Window Position Memory window is used to specify which windows in the Microsoft Dynamics GP application should remember their position, size and state on a per user basis; any window (form) in any dictionary can be added to the list and all sub-windows on selected window (form) will be remembered.

GPPT ships with a small selection of windows pre-configured to be remembered (these are the main transaction and card windows for each module), but more can be added and already selected ones removed using the Window Position Memory window (GP Power Tools area page >> Setup >> Window Position Memory).

When opened, the window takes a few moments to load as it scans all dictionaries. Once loaded the right pane shows the windows which have already been selected; the checkboxes next to them can be unmarked to deselect them:

As an example of how to add a window, I’m going to use add Budget Transaction Entry. To add a window expand the product containing it, which in this example is Microsoft Dynamics GP and click on the series of Financial.

The right pane will change to showing the available windows within the selected series.

Scroll down and find Budget Transaction Entry and mark the checkbox next to it:

Click OK to commit the changes.

There are two buttons on the action pane which are of use:

Default – this button restores the defaults, but any configuration you have done is retained. This means if you’ve added some windows, but, for example, stopped remembering Purchase Requisition Entry, clicking default will start remembering this window.

Reset – this button allows an administrator to reset the remembered window positions for selected users.

Please note, if you remove all remembered windows, the default set is automatically enabled.

UPDATE 20/10/2017 22:58 – I’ve updated the information for Default and added the final paragraph following feedback from WinthropDC.

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

By continuing to use the site (by scrolling or navigating), you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.