Hard Close for Dynamics SL

Last post 03-24-2008 12:55 PM by csims9158. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • 11-06-2007 12:50 PM

    • AM
    • Top 500 Contributor
    • Joined on 11-06-2007
    • Posts 1

    Hard Close for Dynamics SL

    Is anyone using a 3rd party product to prevent the accidental posting of batches to prior periods?   Any issues in implementation?

  • 11-08-2007 3:47 PM In reply to

    Re: Hard Close for Dynamics SL

    Hi AM. I checked in with the Dynamics SL team and they had this to say/

    This feature will be part of the core Dynamics SL product with the next release. Until then, many customers have had great success using the third party offering from Ironware that provides this functionality.

    Hope this helps

    Craig

  • 11-15-2007 4:05 PM In reply to

    Re: Hard Close for Dynamics SL

     

    Hello, My firm, SSI Consulting, offers a Hard Period close module.  The cost is $750 with 18% annual maintenance.   You also need to own the Customization Manager module (most users alrady have this, but if not, it can be added.

     Sincerely,

     Bill Aiton, President

    703-297-5070

  • 11-28-2007 8:15 PM In reply to

    Re: Hard Close for Dynamics SL

    Yes, We recommend the Ironware solution. the majority of our customers are using their Hardclose

  • 03-14-2008 1:46 PM In reply to

    Re: Hard Close for Dynamics SL

    Being new to the Dynamics SL world, the next release they are referring to is something above 7.0 I am assuming? We are on Solomon 6.0 so we are pretty far behind. I just wanted to make sure that 7.0 wasn't the release they are referring to!

    Thanks!

    Lisa

  • 03-24-2008 6:34 AM In reply to

    Re: Hard Close for Dynamics SL

    According to the information in recent Jeff Suwyn's Convergence Presentation (SL-01) on Dynamics-SL V7.0 Feature Pack 1, which will be released sometime in Q4 2008 (by current estimates), the hard close feature is slated to be included.   However, the hard close available in FP1 will be global, not module specific.    The Ironware solution may still be more practical for many folks who need the flexibility to have a hard close in some modules (e.g. inventory, purchasing, AR) but need a soft close in others (e.g. AP, GL).

    Hope this helps.

    Best regards,

    Gail J-N

     

  • 03-24-2008 8:03 AM In reply to

    • Katie
    • Top 500 Contributor
    • Joined on 03-24-2008
    • Caledonia, Michigan
    • Posts 1

    Re: Hard Close for Dynamics SL

    I might also add that in the session I sat in it was stated that the Hard Close functionality that is going to be built into Solomon 7.0 FP1 will prevent people from posting to prior periods.  It WILL NOT prevent them from accidentally posting to the year 3010.  It seems to me that when I when I installed Ironware's product at a client site, it limited future postings as well as prior period posting. 

    I personally have had to correct just as many future period postings as prior period postings.  It's unfortunate that Solomon won't build in a limit to future postings as well as prior period postings.

  • 03-24-2008 12:55 PM In reply to

    Re: Hard Close for Dynamics SL

    I implemented Hard Close at several clients and I agree that it is much more granular in the way it allows you to control by user (and I think group in the newer version) how many periods future and prior you are allowed to post in as well as by module. 

    One issue they were having with 6.5 and 7.0 was with the way it checks to see which modules are registered so that you can control access for the given modules you have.  The issue revolves around the way SL 'bundles' licensing if you go with their Business Ready Licensing (BRL) scheme which prevents the Ironware screen from 'unlocking' certain modules from the screen within the application.  This may have been addressed by now, as I was having this issue with a client back in December.  That being said, this is still a great product I would recommend even when the feature pack is released due the issues stated in the earlier post.

Page 1 of 1 (8 items)