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


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


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 | .... | 1157 | 1158 | (Page 1159) | 1160 | 1161 | .... | 1174 | newer

    0 0

    This year, we launched MetaViewer 7, the newest version of our state-of-the-art document management/paperless automation solution. This new edition also features Touchless Invoice Processing for Microsoft Dynamics AX/365 and GP. Yes, completely touchless!

    MetaViewer 7 brings even more automation to the workplace with immediate feedback from duplicate checking with companies’ ERP solutions. Users no longer need to schedule tasks to be run – MetaViewer 7’s RPA capabilities run tasks constantly and automatically to keep processes streamlined, reduce document processing steps, and eliminate human intervention. MetaViewer 7 is also built on the Windows Workflow Foundation, offering more configuration capabilities, as well as robust, efficient and fast functionality.

    MetaViewer 7 also features Touchless Invoice Processing for Microsoft Dynamics users. The pinnacle of RPA technology, this functionality processes PO documents and routes them through workflow steps – based on pre-determined rules – without any human intervention needed, freeing up your team to work on more pertinent and less menial tasks. Touchless Invoice Processing matches POs in users’ Microsoft Dynamics solution and runs through a set of evaluation rules to determine whether the PO matches corresponding documents within the system. The PO is then routed directly to Microsoft Dynamics. The system runs rules against the corresponding invoice in Microsoft Dynamics, checking whether it is a current invoice, a duplicate invoice, is open against a PO and other pre-defined evaluation rules as determined by your company. If the PO passes each rule, it is automatically routed to Dynamics. If it fails any of the evaluation rules, users receive a report and are able to manually reconcile the PO.

    Want to learn more about MetaViewer 7 and Touchless Invoice Processing? Read the full press release, catch a no-cost webinar or drop us a line at info@metafile.com.


    0 0

    Jen Kuntz offers up a script to clear out unused companies.


    0 0

    The automated process of user provisioning becomes common in many projects. Often, the process includes components outside of Dynamics 365 such as  creating a user in Azure Active Directory, assigning plans and licenses and adding user to AAD groups. All of these can be automated using the Microsoft Graph API.

    In this post, I’ll demonstrate assigning Microsoft Dynamics 365 license to an existing user with Postman. You can later convert Postman requests to JS or C# code or use in Flow and Logic Apps.

    Prerequisites

    1. Have Postman application installed
    2. Have access to Office 365 and Azure environments

    Walkthrough

    1. Register a new Web App/API in Azure AD with a Client Secret and copy Application Id key, callback URL and secret to Notepad.
      Make sure your app is granted the ‘Read directory data’ privilege

      Make sure your app has at least the Read directory data privilege
    2. Set a request to retrieve available SKUs

      In Postman, create a new GET request to the following address, after replacing

      with your actual domain name (e.g. bikinibottom.onmicrosoft.com)

      https://graph.microsoft.com/v1.0/.onmicrosoft.com/subscribedSkus

      In Postman, create a new GET request
    3. Get an Authorization Token

      Before actually accessing the Graph API, you’ll need an access token to authenticate your requests.
      Click the Authorization tab, and set type to OAuth2.0.
      Click the Get New Access Token and select the Authorization Code option for the Grant type attribute In the dialog opened.
      Fill in the Client ID, Client Secret and Callback URL details copied previously to Notepad.

      Fill in the Client ID, Client Secret and Callback URL details

      Click the ‘Request Token’ button to receive a dialog containing an Access Token. Scroll down and clock ‘Use Token’ button

    4. Retrieve Subscriptions

      Click ‘Send’ to execute the

      request which will retrieve a list of commercial subscriptions that your organization has acquired.

      execute the request which will retrieve a list of commercial subscriptions that your organization has acquired

      If you have Dynamics 365 licenses, the following node will be included in the response.
      Copy the skuId value which will be used in the next step.

      If you have Dynamics 365 licenses, the following node is included in the response
    5. Assign License to User

      Create an additional POST

      request to assign license to user with the following URL. Replace the target user principal name 
      (e.g.
      sandycheeks@bikinibottom.onmicrosoft.com)

      <a href="https://graph.microsoft.com/v1.0/users//assignLicense”>https://graph.microsoft.com/v1.0/users//assignLicense

      In the Authorization tab, set the same settings as the first request. As you already have a token, no need to get a new one.
      Add a header of  Content-Type = application/json

      Add a header of  Content-Type = application/json

      Set the request body with the previously copied skuId

      Set the request body with the previously copied skuId

      Click ‘Send’ to send the request and assign Dynamics 365 license to the target user.
      A correct response looks like this

      A correct response looks like this

     

     

     


    0 0
  • 12/27/18--10:38: Purchasing in Field Service
  • Purchasing In Field Service Hi Everyone Let's discuss about the Purchasing phase in Microsoft Dynamics 365 for Field Service. As the resources are in the field and perform operation and then eventually...(read more)

    0 0

    Hi Everyone, Today i am going to discuss few points about the Processing Returns in Field Service. There are three ways for returning a product - Return to warehouse - Return to vendor - Change equipment...(read more)

    0 0

    This was a internal request from support team to quickly fix the certificate expire issue. I would like to post it here in case you need it. Please note this should only apply to your Dev VHD, and strongly recommand you create a checkpoint before proceed.

    One script for all steps(renew certificate,grant permission, replace in config, reset iis and batch)

    Function Update-Thumberprint

    {

        Set-Location -Path “cert:\LocalMachine\My”

        $oldCerts = Get-childitem | where { $_.subject -match “DeploymentsOnebox” -or $_.Subject -match “MicrosoftDynamicsAXDSCEncryptionCert”}

        $ConfigFiles =

        @(“C:\AOSService\webroot\web.config”,

          “C:\AOSService\webroot\wif.config”,

          “C:\AOSService\webroot\wif.services.config”,

          “C:\FinancialReporting\Server\ApplicationService\web.config”,

          “C:\RetailServer\webroot\web.config”

          )

        foreach ($oldCert in $oldCerts)

        {

            $newCert = New-SelfSignedCertificate -CloneCert $oldCert

            #consider to delete the old cert

            $keyPath = Join-Path -Path $env:ProgramData -ChildPath “\Microsoft\Crypto\RSA\MachineKeys”

            $keyName = $newCert.PrivateKey.CspKeyContainerInfo.UniqueKeyContainerName

            $keyFullPath = Join-Path -Path $keyPath -ChildPath $keyName

            $aclByKey = (Get-Item $keyFullPath).GetAccessControl(‘Access’)

            $permission = “EveryOne”,“Read”, “Allow”

            $accessRule = New-Object -TypeName System.Security.AccessControl.FileSystemAccessRule -ArgumentList $permission

            $aclByKey.SetAccessRule($accessRule)

            Set-Acl -Path $keyFullPath -AclObject $aclByKey -ErrorAction Stop

            foreach($configFile in $ConfigFiles)

            {

                (Get-Content -Path $configFile).Replace($oldCert.Thumbprint,$newCert.Thumbprint) | Set-Content $configFile

            }

        }

    }

    Update-Thumberprint

    iisreset

    Restart-Service “DynamicsAxBatch”

    Please copy all the script and run in powershell via administrator previligge.

    Each time you run this script, it will create a new set of certificates. So do not repeat it.

    Hope it helps.


    0 0

    Friends You can Follow this technique to Solve Problem in Year 2019. I hope you will able to understand.

    Problem solving process


    0 0

    The fourth and last skillset in Manage the Attract and Recruiting Processes (25 – 30%) is; Create and manage offers Define offer settings; maintain the status of the offer; start the onboarding...(read more)

    0 0

    Right before Christmas I saw a blogpost by Jeremy Vyska which got my attention. It highlighted some changes in the December version of the Business Central on-premise licensing guide

    In the October version a new license included a free CAL for an External Accountant user and one CAL for a System Administrator user. In the November version only a free one for the External Accountant. In December no free users are included!

    Jeremy also contacted Microsoft and got the answer that this was no mistake on their side:

    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.

    I was just as "surprised" to read this. So, I tried to figure this out on my own. With the help of the internet, it was quite easy to find the same versions for the licensing guides for Business Central. And they just confirmed what I already knew from Jeremy's website. It has been removed!

    But it's not something Microsoft has been trying to hide. It's in the change long on the last page (Appendix D). The external accountant/system administrator has been removed and is only included in subscription, non-perpetual on-premise licenses.

    The Subscription Economy is coming

    Despite my initial response to this licensing update, then, when we think about it, this move makes a lot of sense.

    Microsoft is no longer just a software company.

    Sure, they are stilling developing some the best software in the world. But as a company they are moving away from making most of their money selling software towards making them on selling services through subscriptions. That be Xbox, Office 365, Dynamics 365, Azure or one of the many other services you can buy from Microsoft.

    Microsoft are not alone. They are part of global trend called the subscription economy. Not only the software industry, but almost all industries are trying to go from selling products to sell services. You don't buy you car, you lease it. You don't buy a phone, you get it as part of a subscription. You continue, the examples are plenty and more keeps coming. The global subscription economy index has grown from base 100 in 2012 to almost 300 by Q2. The US retail sales index only grew from 100 to 130 in the same period.

    The trend is clear, we are going to see much more of this in the future.

    How long can we buy perpetual Business Central licenses?

    With Microsoft's goal of getting as many customers on subscriptions, then it means making subscriptions more attractive than buying a license.

    One way would be to make subscription licenses much cheaper than what they are now. But that would mean less profit to Microsoft. So not the ideal way to a business.

    Another way would be to simply stop selling perpetual license, but that would most like also mean less profit to Microsoft, if the market, as I believe, is not ready yet. I had seen that this would have happened when Dynamics NAV became Dynamics 365 Business Central back in October. But luckily it did not. We can still buy BC licenses in 2019.

    One user at the time

    The way it seems that Microsoft are taking is to gradually make the perpetual license more expensive than the subscription license. They expect that doing it in small slices will not scare off too many partners or customers). One user at the time, so to say.

    We must be ready for a future where perpetual licenses are not available. A future which may be here sooner than we expect. How many had thought Microsoft would announce the retirement of C/Side in only 1-2 years?

    The external user problem

    This recent license change means that the cost of a Business Central On-Premise Perpetual (non-subscription) license has gone up with the cost of at least two CAL's. That's not peanuts, if we compare to the Dynamics NAV days.

    The problem is not so much the external accountant CAL, at least not if this user is doing the actual accounting. If they used the system to enter data etc., then they also took up a concurrent user here.

    That's not the case with typical Dynamics NAV customers, who have their own accountants in-house. Instead they need to be able to give access to employees from external auditors and employees from NAV partners, often multiple consultants, developers and supports from multiple partners.

    With NAV's concurrent licenses it was never really a problem to give the external accountant, auditors or partners a user access. Most companies have a small pool of extra logins, they can use for both external partners and their own employees who only use the system part of the time. And even if all CAL's where in use, then we could load our partner license temporarily in C/Side and still access the system.

    Business Central is more expensive than NAV

    The only reason why this is a problem is because BC count number of named users, not concurrent users. It typically makes all BC licenses much more expensive, than a similar NAV license. Not only because of the external users, but because all companies have users who only uses the system a small part of the day or maybe just a few times per month. Even if some users would be able to use team/limited licenses, then more full licenses would still be required.

    I have worked in companies where we had about 1200 named uses, but less than 300 concurrent licenses and (almost) never had a problem. Team/limited licenses would not change much here.

    Previously concurrent licenses were the standard in most of the IT industry. Today everybody, not only if sold as subscriptions, sells their CAL's as named. Not only Microsoft. NAV were one of the few remaining concurrent licenses in Microsoft.

    I do not believe that train can be stopped now. Named users are here to stay.

    And as long customers feel that they are actually getting "something" for their CAL money, then I also believe that named users is not that bad.

    Subscription Economy and Named Users are technical excuses

    While the subscription economy, named users etc. all makes full sense when it comes to actual users, then not when it comes to require customers to buy more licenses, just allow them to get support, either from partners or accountants/auditors. That's basically a just a technical excuse to make the license more expensive.

    I say it's a technical excuse because it could be solved technically if they wanted.

    In the cloud version of BC Microsoft have solved the "external user" problem, despite named users. Here access is managed. Accountants via the accountant portal and partners via the partner portal. Except if the customer has more partners supporting them. Here Microsoft have the control over the users.

    On-premise installations of Business Central are outside of Microsoft's control, including their users. That means that technically it is not possible for Microsoft to control if the users are external or internal. If external users where free and everybody could create them then what would prevent customers from creating all their new users as external?

    I understand the dilemma Microsoft is in. I don't think they are doing this to make a lot of profit.

    They need a way to ensure that named user accounts for partners are not used by users who should pay. The easy way is just to make them all count.

    A technical solution

    If Microsoft wanted, then I am sure that they could find a technical solution to this technical problem.

    Something like having a "partner key" which had to be "imported" when creating (and using) a "partner account". Like we had to do in C/Side, where we could import our Partner AL-key temporary. If Microsoft could issue named keys to partner employees, then I'm sure their BC developers easily could come up with a way to authorize such accounts. Eventually using the same personal Microsoft account used by the user everywhere else.

    Ideally the same solution could be used in the cloud too. Instead of having "one named" account for the partner, this would allow for more partners to access the same tenant.

    It would also give Microsoft to know more about both their partners and customers, and prevent "un-authorized" partners access.

    I am just afraid that even if this would not take up too much time to do, then it is primary for the on-premise version and will therefore be low on their list of priorities. I'm sure they have plenty of things on that list already.

    What will customers do?

    If customers will have to dedicate a user for the partner, then I'm sure that this is going to be a "company account", a single user account to be used by all the employees from the partner. And that there will be lot of enabling/disabling users.

    From a security perspective that has always been bad practice. GDPR may even make this practice illegal, but I still think that it's the path most will chose. Cost over security or best practice.

     

     

    Please Microsoft, let us know your reasoning behind this policy change

    Are you out to make more money on partners? Is on-premise supposed to "die" soon anyway, so no reason to prioritize it? Or what is the reason?


    0 0

    Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

    The eighteenth new feature is Letter Writing Assistant in Web Client. This feature adds one of the few remaining areas that wasn’t previously accessible to the web client.

    The Letter Writing Assistant is available via SmartList; for example, run a Vendors SmartList and the click on the Word button and click Prepare a Creditor Letter:

    SmartList prepare a Creditor Letter

    Select the type of letter to produce and click Next:

    Letter Writing Assistant - Letter Templates

    Enter the name, title and communication fields and then click Finish:

    Letter Writing Assistant - Completing the Letter Writing Assistant

    An open/save bar will be displayed, assuming you’re using Internet Explorer; click Open:

    Open document

    Microsoft Word will open and show the mail merged letter:

    Microsoft Word with the mail merged letter

    I make little use of the Letter Writing Assistant as it can only produce documents into Word and not email them, but I know some clients have used it in the past. As this was one of the few areas of Dynamics GP not available in the web client, it is good to see it added. It’s always good, in a demo, to be able to say that all the functionality is available in both the desktop and web clients.

    Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

    Read original post Hands On With Microsoft Dynamics GP 2018 R2 New Features: Letter Writing Assistant in Web Client at azurecurve|Ramblings of a Dynamics GP Consultant


    0 0

    Machine Learning is everywhere. It does promise a bright future with auto-pilots and self-driving cars. And it brings nightmares with facial recognition and self-fulfilling prophecies. But because Dynamics...(read more)

    0 0

    Introduction: When developer need to use the js framework in the web. With the Dynamics 365 portal and liquid templates you can utilize the development approaches with those frameworks within your liquid...(read more)

    0 0

    A selection of the latest insights from the Dynamics GP blogs


    0 0

    A selection of the latest insights from the Dynamics 365-AX blogs ...read more


    0 0

    A selection of the latest insights from the Dynamics 365-CRM blogs.


    0 0

    Recently, I changed my alias in Office 365 portal. I did not add or delete an username, but changed the login alias I was using, with a new domain. All of a sudden, my Dynamics 365 for Talent account did...(read more)

    0 0

    D365Tour Newsletter - December 2018 Flow Creating a Custom Mockaroo Flow Connector MSDyn365FO What’s new or changed in Dynamics 365 for Finance and Operations version...(read more)

    0 0

    Microsoft's launch of Dynamics 365 Business Central in 2018 set in motion big changes in the NAV community


    0 0

    The heart.

    It is an often-used analogy for something central and indispensable to an operation. In the Manufacturing realm, the very heart of a business is the Shop Floor. It’s where “the magic happens.” After all, it’s your product that defines you, and the shop floor is where that product is born. All the supplies in the world and the most strategic distributor network possible won’t help you at all if you can’t fulfill promises and meet demand.

    Learn about emerging trends in manufacturing in this free white paper from Microsoft »

    At Fabtech 2018, we gave a presentation that showed how Dynamics 365 provides tangible, measurable benefits at the shop floor level, and how using it to bring your “heart” into top condition can put you in a prime position for growth and success. Let’s take a closer look:

    Faster Information Flow

    While the workers on the shop floor have a huge role to play in the success of your manufacturing line, there are many decisions to be made behind the scenes, and those decisions depend on knowing what’s happening right now on the shop floor. Dynamics 365 gives you visibility into production processes that are being performed. You can sort by order number, resource, product, and status. From there you can set the priority of specific operations, and even coordinate operations across divisions.

    Transparent Problems and Variations

    A large contributing factor to manufacturing waste is the slow detection of problems and variations in labor hours and material consumption. If these spike, it’s indicative of a potential production bottleneck. This problem is compounded when there are multiple stages running concurrently, when processes are interdependent, and so on. With Dynamics 365, online exchange of information immediately shows deviations and problems, so reaction time can be faster. Drill down to identify, review, and validate hours and material consumption variations. Track finished quantity variations. Quickly create corrections, eliminating bottlenecks and ensuring smooth production, filling quotas and reaching goals.

    Cost Reduction

    Who doesn’t like saving money? Dynamics 365 brings major cost reductions by improving efficiencies across the board. And data critical for process improvement and decision making is collected for the management officials who will ultimately decide on manufacturing and process improvements. For example:

    • Time spent by management staff is better utilized, since the information flows directly from the floor instead of individuals having to go there to find it.
    • Training costs are reduced based on an easy Touch Screen Interface for the end user.
    • Production Time Logging for processing costs is done based on the floor input, not on “guesstimates”.
    • Secure Logins to a Touch Job Card Device provide accountability and security.

    Measurable Return on Investment

    Implementing improved business processes and fostering collaboration between team members and management facilitated by Dynamics 365 brings dividends that can be counted. Here’s a sampling:

    • Total visibility and control over plant environment
    • More efficient, streamlined operations and lowered manufacturing cycle times
    • Data-driven, higher quality production
    • Immediately actionable, proactive data and analytics when employing a real-time SFC system
    • Empowered supervisors and managers
    • Increased operator motivation, productivity and performance
    • Improved accuracy in reporting on resource status, workflows, inventory and human resources
    • Accurate updates on labor and machine usage
    • Improved valuation and costing capabilities
    • Reduction of excess labor costs
    • Reduction of payroll computational errors
    • Reduction of work in process inventory

    As you can see, Dynamics 365 has far-reaching capabilities that unite the disparate departments in your organization, always listening to your “heart” and ensuring its optimum health.

    Want to learn how to take advantage of these benefits? Contact us to find out how Dynamics 365 can transform your manufacturing operation into the lean machine it should be!

    Learn about Dynamics 365 for Manufacturing »

     

     

    By Turnkey Technologies, Inc. - Microsoft Gold Partner headquartered in St. Louis, Missouri.


    0 0

    In AX 2012 there are two types of Financial Dimensions: a) Custom type b) Built in types (department, workers, customer, vendor, projects,etc.) Below is an example of how to import custom type financial...(read more)

older | 1 | .... | 1157 | 1158 | (Page 1159) | 1160 | 1161 | .... | 1174 | newer