web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Adding optional fields in POP entry screen

(0) ShareShare
ReportReport
Posted on by

We are working with a client that is also looking at MAS500.  GP Analytical Accounting does not cut the mustard nor does Extender.  The cleint must be able to track additional UDFs (yes/no, pre-defined drop down selection lists, etc.) on POP lines, but does not necessarily need to go to the GL distribution level.  So, they need to easily setup UDFs on both POP HEADERS and LINES. 

Also, they need to be able to feed into these fields easily with the eRequester add-on Requisitioning product they are going to potentially purhcase.  Lastly, they need to be able to access these fields easily via SmartList and Excel Reporting Services for user/government reporting.  The client does not want to be locked into having a programmer make changes each time.  MAS500 allows this all natively.

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    25,195 on at
    Re: Adding optional fields in POP entry screen

    I am not sure why you stated that Extender does not work for your client.  It feeds SmartList, it is exposed to Excel Report builder (Create Views in Extender...makes this MUCH easier), and the new windows/forms can be attached to headers and/or lines very easily.

  • callen Profile Picture
    4,595 on at
    Re: Re: Adding optional fields in POP entry screen

    I think the issue is with eRequester, not GP. The interface from eRequester will need to be customized to hit the Extender tables.

  • Sharon Paul Profile Picture
    on at
    Re: Re: Adding optional fields in POP entry screen

    I guess the feeling is that the Extender fields are clunky in that they do not show up on the same form and appear in alternate windows, making it difficult for data entry.  Also, the fact that Extender stores the values in separate tables that are rather difficult to deal with from a reporting/programming/interface stanpoint as opposed to MAS doing it a bit more seemlessly.  My colleague is actually working on this so I'll pass along the thoughts.  I'm not really a MAS pro but apparently their optional fields are handled cleaner in the MAS500 product than in GP?  Not sure.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans