Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog

Channel Description:

A one stop shop where the Microsoft Dynamics ecosystem can learn, share, connect and network with others within the Community. Peer to Peer discussions , product demonstrations, blogs & videos.

older | 1 | .... | 1150 | 1151 | (Page 1152) | 1153 | 1154 | .... | 1174 | newer

    0 0

    If an organisation offers a service, it could be that a tiered service structure is offered. So, for example, the Bronze package could give 5 cases a year, Silver could be 25, with a Gold or Platinum package...(read more)

    0 0

    The third skillset in Manage the Attract and Recruiting Processes (25 – 30%) is; Schedule and manage interviews Request candidate availability; Identify options for defining the interview;...(read more)

    0 0

    In tip #1213 we walked you through a long winded way finding out where and when the Flow button was pushed. It involved using lattitude and longitude of the user’s location and calling Bing Maps API.

    As it turns out, if you are only after the local time, there is a much simpler method. When a flow is invoked using manual button, trigger tokens contain, among other values, local date and time at the location where the button was invoked. These values are accessible using the following expressions:

    • Date as triggerBody()['key-button-date']
    • Timestamp as triggerBody()['key-button-timestamp']

    The entire brouhaha can now be reduced to:

    Flow telling the local time

    The only gotcha is that the property key-button-timestamp does not exist when the flow is run from the browser, it is only available on a mobile device. When testing, do at least a single run using a mobile device and then re-use this test run data in subsequent testing.

    (Cover photo by Luke Chesser on Unsplash)

    0 0

    Everyone knows how to edit the sitemap on a custom app, but did you know you can access the Sitemap Editor to edit the sitemap of the default custom app? Let Gus show you how you can quickly create a solution...(read more)

    0 0

    Occasionally we might get the below error in our SSIS Package. [Dynamics CRM Destination [2]] Error: An error occurred with the following error message: “System.AggregateException: One or more errors...(read more)

    0 0

    Muchas veces el inicio de Visual Studio y la apertura de un proyecto de Dynamics 365 toma un tiempo realmente muy considerable, para evitar este inconveniente y mejorar el rendimiento en la apertura de...(read more)

    0 0
  • 12/18/18--05:30: Quick Journals
  • The last couple of #TipTuesday posts have been around some older “new” features – copy journal entry and backout/correct journal entry. Today I thought I would write a quick tip post around one of the lesser known options for creating journal entries in Dynamics GP: quick journals. Next week for my last #TipTuesday of the year, I’ll have a post about the other option which is clearing entries.

    What is a Quick Journal?

    Quick Journals are a type of journal entry template, where the account numbers for common journal entries are set up in advance in a template, with a default offset account.

    Default Offset Account? What does that even mean?

    This may be “new” terminology to you if you have not used a Quick Journal before. An Offset Account is a GL account where the ‘balance’ of the journal entry will be posted.

    Take an accrual for instance: the obvious choice for the offset account on an entry for accrued liabilities would be the Accrued Liabilities account, assuming you only have one. The template itself would be listing all of the other GL accounts typically being accrued, and it would not list the Accrued Liabilities account, since that would be the offset. Then, during the actual entry, the user is merely entering in the amounts for the “debit” side of the accruals and the credit is the balance to Accrued Liabilities.

    Quick Journal Setup

    First, in order to use Quick Journals, there is a setup window to create the “template”. It’s under the Financial page > Setup > Quick Journal. Each Quick Journal has an ID and description. The Journal ID becomes the batch when the Quick Journal is posted so I would recommend using somewhat meaningful names for the IDs, as much as the length of the field allows that is. The description is used only for reference by the user when selecting a Quick Journal ID from the list, during transaction entry.

    Quick Journal setup

    The next two fields are the default Source Document and Reference fields for the journal entry. This is very handy if you use unique source documents for any purpose as the user would not need to remember to change it.

    For the reference, the tip I usually gave to my clients was to think about the description you want on the resulting journal entry, and if you typically would add a month or period name, do something like I show above where I leave the end of the reference blank for editing during use.

    Next, select the Offset Account. Note that the field is required, both in the setup and in use in the Quick Journal entry itself. If the type of entry you have in mind wouldn’t always use the same offset, then you will want to mark the Allow Override box, to allow the end user using this ID to change that GL account if and when required. There are going to be instances where you never want it overridden and others where you often override, so plan accordingly when you create the IDs to have controls where you need them. Beside the Offset Account is the Break Down Allocation account option, which would display (“preview”) the results of what the allocation account would be when posted, on the edit list or posting journal.

    Finally, the entry itself, in the line item detail section of the window. This is where you would list the various GL accounts that could be used in this Quick Journal. A user can add more GL accounts during entry as well as leave some accounts blank (zero $) during entry so the choice really is about efficiency: is it better to list off the accounts that are most likely to be used or all accounts so the user has to scroll through a longer list? All I would recommend is put the accounts in an order that makes sense for the journal entry you have in mind. It’s intended to be making it easier to record journal entries so why not think about the order you put the accounts in here in the first place?

    Using a Quick Journal

    Once you have one or more Quick Journal IDs set up, the way to use them is via the Financial page > Transactions > Quick Journal. Quick Journals use the same Next Journal Entry number as standard journal entries. Once you select a Journal ID from the lookup, the values from the setup are brought into the window as displayed below.

    In this example below, I had not marked Allow Override on the Offset Account in setup, so you will see the account is greyed out. To record my entry, I simply type in everything else I want in my accrual example, and I put in the amount in the Control Balance field. At this point I can save it (but not in a “batch” that I create) or I can post it. There are no traditional batches to review like there are with regular journal entries. More on this to come…

    Quick Journal entry no override

    The next example is what the Quick Journal Entry window looks like if Allow Override is marked in setup: it’s now changeable by the user creating the entry.

    Some gotchas…

    There are definitely some quirks to Quick Journals! I believe they have their uses, but they have some odd qualities that are things you may not realize until you play with them for a while.

    No batches, but you can save them!

    As I mentioned above, once you enter what you want, you can save the entry or you can post it. Saving it is seemingly putting it into “no man’s land”, however, they are save-able and thus there is a chance for some segregation of duties if you wanted users to enter but not post Quick Journals.

    Saved entries are visible in Series Post but not Batch Entry

    To continue on the segregation comment above, security could be defined to allow users to enter & save Quick Journals but not post them (theoretically) and then someone else could be posting them from the Series Post window. The flaw in this plan would be there is no great way to get edit lists, which would be the traditional workflow for many organizations (user enters transactions in a batch, someone reviews an edit list and posts the batch). If I were to try this, I would likely create a Financial Transaction smartlist to review unposted Quick Journal entries in lieu of a single batch edit list you might expect from other modules.

    Edit Lists are weird

    So, at first glance it seems like you can’t print an edit list. After all, there is no “batch”. However, if you save an entry, and then re-select it, there is a Print button on the Quick Journal entry window where you can print an edit list. And get this: since the Quick Journal ID is the batch ID, if you have entered and saved multiple Quick Journals with the same Journal ID, the edit list will show all of them. Yes, that’s what I call a little weird. Otherwise, there is no way to print an edit list for a bunch of entries that use different journal IDs. Strange but true.

    Transaction balance cannot be zero

    Here’s one error message a user could get, if you mistakenly created a Quick Journal with the intent of having a balanced journal entry. (What are you thinking? LOL). If you were to create an entry where the detailed lines contained a net-zero balance, so that there is nothing for the Offset Account, you would get this error message: “The transaction balance cannot equal zero.”.

    Control Balance must match, or be left empty (zero)

    The last of the oddities is the Control Balance field on the Quick Journal Entry window. It’s not required, or is it? Well… it’s been a while since I’ve used Quick Journals and I’m testing/writing this with GP 2018. I don’t recall it working this way but here goes: you can leave the Control Balance at zero and it will allow you to post the entry OR the Control Balance must be the amount that will hit the Offset Account. This error text if it doesn’t match, would say “You cannot post. Transaction balance does not equal the control balance.”.

    So…. naturally I wonder why one would bother entering a Control Balance if I don’t have to? Hmm… things I’ll likely never find the answer to. I realize that having a user go through a specific steps of entering a control balance and then typing in the amounts for the entry itself does enforce a certain amount of rigour in the process and there is value in that, I just don’t know how many departments work that way in reality these days.

    That is all I can think of to write about the unique option we have called Quick Journals! Enjoy!

    0 0

    Are you an Applicable Large Employer that is required to comply with the Affordable Care Act? In addition to the benefits of getting your employee ACA reporting for the IRS (1095-Cs) done before the busy W-2 season begins, there is now another great reason to get started early on your year-end ACA activities: the US postal service has announced a postage rates increase effective January 27, 2019.

    The cost of a standard stamp for US mail is going up from $0.50 to $0.55. This additional 5 cent cost may not be big bucks for many employers, but, it does add up. For example, if you have to distribute 4,000 forms to employees, this equates to $200.00. For budget-conscious employers, you can avoid this additional cost by getting your forms in the mail to employees prior to January 27th. So, despite the IRS extending the deadline to furnish ACA forms to employees from January 31, 2019 to March 4, 2019, it makes sense to distribute these forms early if at all possible.

    Users of the Integrity Data ACA 1095-C distribution service can avoid the 5 cent postage rates increase as well. The cutoff date to ensure your forms are mailed to employees prior the January 27th rate increase is January 21st. Getting your forms sent to employees from within our ACA application is easy and doesn’t involve you licking and stuffing envelopes. This is true for our full-service ACA offering as well. If you’re not familiar with this offering where we do ACA compliance on your behalf, check out our website. Unless otherwise negotiated, all forms sent to employees on or after January 22, 2019 will be billed an additional $0.05 per form to cover the additional postage.

    Based on our standard mail distribution pricing, Full-Service and Subscription-Based Customers will pay $2.80/form on or after January 22, 2019 and “Fulfill & File Only” customers will pay $3.30/form or after January 22, 2019. For any questions in this area, please contact

    0 0

    In my previous post I wrote about how to use disposable context , which is very useful in cases where we want pass an extra parameter to the method. In this post we will see how it can be utilized to pass...(read more)

    0 0
  • 12/18/18--12:39: New home
  • I have moved my blog to Dynamics 365 Community .(read more)

    0 0

    As we have multiple Microsoft Dynamics 365 Business Central On-Premise customers coming online this year that have opted to purchase CALs (the perpetual license model) rather than SALs (the subscription license model), this topic was very important to us to better understand how we can support our customers.

    You may have followed along with my November / December posts about this issue, pardon the recap (I’ll note where you can skip ahead to):

    When the new Named User versus Concurrent was announced with the release of the On-Premise edition, I was concerned about how we would access customer’s systems as a partner. We have a number of customers today on Dynamics NAV who have precisely the number of Concurrent User Licenses that they need, so when they need us to support them by connecting to their production system, we have to ask them to have someone close their session. With Named Users, that won’t work. So, I was excited to see this in the Licensing Guide, the October version:

    Very clear cut. The section covering the SAL is back on Page 3, so this is specifically about On-Premise CALs.

    At the end of November, we had closed deals on new customers and were beginning to take steps to support them. Immediately, we ran into the fact that everything highlighted above is not true. Support case opened, and here we are a month later.

    Note: This highlighted passage was still present in the November 2018 version of the guide:



    I have received what the support team called the “official / final answer”:

    We don’t offer free licenses for perpetual on-prem licenses. The mentioned text in the licensing guide, speaks to SAL which is used for subscription access license not perpetual.

    There are no plans to update the licensing guide which means it will not be adjusted / nor corrected.


    Just for laughs, I checked, and yes, the Licensing Guide (PartnerSource login required to access) has been updated for December 2018:

    I highlighted where the now removed paragraph used to be.

    So, there you have it. There is no System Administrator or External Accountant license when running On-Premise Perpetual (CAL). Partners needing to access production systems officially need to have a fully licensed Named User (presumably, any other creative solutions are not permitted).


    I, for one, look greatly forward to explaining to customers that we have to screen share with them to touch their system like it’s the 90’s.

    I also imagine I’ll enjoy this battle all over again in the sequel when we have a customer select SAL licensing and we allegedly should have “System Administrator User” access again…

    0 0

    Ever since the web client was first released for Microsoft Dynamics NAV 2013, and subsequently in Dynamics 365 Business Central, it has been incrementally improved with each release. As the feature...(read more)

    0 0

    Dynamics Communities is finally planning to bring the User Group Summit conference down under to Melbourne, Australia on 21-23 August 2019. No, this is not an April Fool post, it is true. However, whether...(read more)

    0 0

    Introduction: In this blog we will demonstrate how to set visibility of a field in Dynamics CRM based on Security Roles using JavaScript. Implementation: Step 1: First we create a security role, Here for...(read more)

    0 0
  • 12/18/18--19:55: Remove Unused G/L Accounts
  • A large number of unused G/L accounts can slow down reporting (especially in Management Reporter w/ datamart) but is also down right ugly and muddies up day to day entry. Outside of clicking through each...(read more)

    0 0

    Since the launch of consultancy service listings on AppSource last year, we've had great interest from partners in listing their Dynamics 365 Business Central services on AppSource . In select markets...(read more)

    0 0

    Here’s one for the SQL script vault. As of GP 2018 R2, GP STILL does not provide the customer email address as a field in Smartlist. Here are a few quick options to get what you’re looking for: Option...(read more)

    0 0

    Hi Readers,

    I hope you were able to follow what we have done till now on Last articles in this series. If you haven't read the earlier article, then Refer to Table of content.

    Till now we have developed some new tables and pages and customized base objects using Table Extension and Page Extension.

    In this article, we will Publish this extension to see what we have done in the application.

    Read Complete Article »

    0 0

    Building applications to work with NAV/BC is a pretty good idea. When customization becomes too difficult, creating a new app may be the good idea. To do so, you're not alone. Webservices are there...(read more)

    0 0

    I am about to take the MB2-719 certification, this certification covers the Dynamics 365 for Marketing Application. I plan to create a series of blog posts that collectively should help anyone else preparing...(read more)

older | 1 | .... | 1150 | 1151 | (Page 1152) | 1153 | 1154 | .... | 1174 | newer