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 | .... | 1101 | 1102 | (Page 1103) | 1104 | 1105 | .... | 1174 | newer

    0 0

    Duplicating of record is one of those nifty features that doesn’t exist in Microsoft Dynamics 365 CRM out-of-the-box. Using Zap Copy Record App you can Copy, Clone or Duplicate records in single...(read more)

    0 0

    My latest article for MSDynamicsWorld.com was published today. It talks about the October ’18 release of the Dynamics 365 Portal product, which includes SharePoint and PowerBI integration, as well...(read more)

    0 0

    In this post, we’ll see how to upload data in CSV file to D365 instance using Azure Data Factory. We’ll need following Azure resources for this demo: Azure Data Factory Blob Storage ...(read more)

    0 0

    Suppose we have already configured Portal, created contacts and associated KB article to the Portal. Now the scenario we want to implement is we want a particular user to have access to all the KB article...(read more)

    0 0

    We have SSIS jobs which retrieve incremental data from Dynamics CRM 365 and run every 2 hours. Recently we observed few jobs were failing with request channel timed out error. We figured out that these...(read more)

    0 0

    Find resources that help you build and sustain a profitable cloud business, connect with customers and prospects, and differentiate your business. Read previous issues of the newsletter and get real-time updates about partner-related news and information on our US Partner Community Twitter channel.

    Looking for partner training courses, community calls, and events? Refer to the Hot Sheet training schedule for a six-week outlook that’s updated regularly as we learn about new offerings. To stay in touch with us and connect with other partners and Microsoft sales, marketing, and product experts, join our US Partner Community on Yammer.

    New events and webcasts this fall

    Upcoming US Partner Community calls

    New posts on the US Partner Community blog

    Learning news

    MPN news

     


    0 0

    One of the main new features of Microsoft Dynamics GP 2018 R2 is the option to use the Microsoft Dynamics 365 Business Central Intelligent Cloud Insights. This leverages the Business Intelligence and Artificial...(read more)

    0 0

    Hi Readers,

    We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions.

    After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-prem) from NAV 2017.

    For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process.

    After the Merge Process, the next step is data migration. Let's discuss those steps.

    Direct Upgrade to Microsoft Dynamics 365 Business Central (on-prem) is from following versions -
    1. NAV 2015.
    2. NAV 2016.
    3. NAV 2017.
    4. NAV 2018.

    Read Complete Article »

    0 0

    I have had a few 8.1 dev boxes where the debugger just wouldn't hit any breakpoints.

    The cause is this related to this setting in Visual Studio:


    On the new boxes where I have had the problem "Only specified modules" was active, but no modules were specified. You can change this to "All modules, unless excluded" or figure out precisely which modules add.

    0 0

    An option for providing users outside your organization with access to your instance to Dynamics 365 is to use Azure AD (Active Directory) . You add them as guest users in Azure AD,  assign them a Dynamics...(read more)

    0 0

    What I really miss in X++ is the ability to throw exception objects. If you throw an exception in X++, it’s just a number defining what kind of exception it is, which usually says just “Error” (Exception::Error). You also typically add a message to infolog, but the message in infolog and the exception don’t have any link.

    Other object-oriented programming languages (such as Java, C# or Python) do it in a much better (object-oriented) way. You throw an object, which contains a lot of information about the error – the type (such as FileNotFoundException), a message, extra details such as the argument name of ArgumentNullException, a stack trace showing which sequence of calls led to the error and so on.

    What I consider the most important is the type. This is necessary for meaningful recovery from errors. For example, you’ll go back to user when an error says that an input is invalid, while you may wait a while and try a request a bit later if you know that the error is about a network failure. If all you know is that there is an error, you can’t handle different errors in different ways; you can either stop execution when an error occurs or you’ll ignore all errors. Obviously, neither is ideal.

    And other information besides type are is useful too. You may want to log stack trace of where the exception was thrown (not caught), you may want to know which parameter has a wrong value and so on.

    I mentioned several times in previous blog posts that D365FO runs on the .NET (CLR) platform and you can catch exceptions objects of CLR exceptions (see Catching exceptions in AX 7). While this is useful, you can’t throw such exceptions from X++, therefore it alone can’t solve our problem.

    But making it possible isn’t difficult. Let me show you my proof of concept.

    What I wanted to achieve:

    • Ability to throw “normal” .NET exceptions from X++. For example, I want to throw ArgumentNullException rather than just error(“Wrong parameters specified”).
    • Ability to define and throw custom exceptions, specific to the business domain of D365FO.
    • Ability to catch these custom exceptions in the usual way.
    • Simple syntax for throwing these exceptions.

    Throwing .NET exceptions from X++ can be easily done with a little C# class library. We can throw exception objects from C# and we can call C# methods from X++, therefore we can  instantiate an exception, pass it to a C# method and throw it from there.

    This is the class in C#:

    publicclass ExceptionHelper
    {publicstaticvoid ThrowException(Exception ex){throw ex;}}

    You could call it from X++ like this:

    ExceptionHelper::ThrowException(new ArgumentNullException("_name");

    While this works, it doesn’t look natural. I wanted something similar to throw error(“…”). We can’t throw exception objects with throw keyword in X++, but we can do this:

    throw exception(new ArgumentNullException("_name"));

    exception() is a global function calling the exception helper. It’s implemented in an extension of Global class:

    [ExtensionOf(classStr(Global))]finalstaticclass Global_ManagedExceptions_Extension
    {publicstatic Exception exception(System.Exception _ex){
            Goshoom.DynamicsAX.ExceptionHelper::ThrowException(_ex);
            // The return statement is never called because an exception is thrown above,// but it makes the method compatible with the throw statement.return Exception::Error;
        }}

    The fact that it returns Exception::Error makes it usable in the throw statement. Calling just exception(…) has the same effect as throw exception(…), but the latter is nicely consistent with throw error(…).

    When we can throw exception objects, why should we limit ourselves to existing exception classes? We can easily define our own, specific to our needs in D365FO.

    For demonstration, I’ve implemented FieldEmptyException, where you can provide information about the field and the record in question. Later you can use this information for logging, for highlighting failing records or anything you like.

    For example, here I’m checking if a record has a value in the Email field and I throw a FieldEmptyException if not.

    SysUserInfo user = ...
     
    if(!user.Email){throw exception(new FieldEmptyException(fieldStr(SysUserInfo, Email), user));
    }

    Then we can catch FieldEmptyException and react to it, instead of catching all errors by the universal class catch (Exception::Error). We also have all details available when we catch the exception, as demonstrated here:

    This infolog was generated by the following catch clause:

    catch (fieldEmptyEx){if(fieldEmptyEx.Record){setPrefix("We can log all these details:");
            info(strFmt("Exception type: %1", fieldEmptyEx.GetType().Name));
            info(strFmt("Message: %1", fieldEmptyEx.Message));
            info(strFmt("Table: %1",tableId2Name(fieldEmptyEx.Record.TableId)));
            info(strFmt("Field: %1", fieldEmptyEx.FieldName));
     
            SysUserInfo user = fieldEmptyEx.Record as SysUserInfo;
            if(user){
                info(strFmt("Data from the table: user ID %1, RecID %2", user.id, user.RecId));
            } 
            info(strFmt("Stack trace: %1", fieldEmptyEx.StackTrace));
        }}

    But if you want to use the usual catch (Exception::Error), you can! I’ve implemented FieldEmptyException as a specialization of ErrorException, therefore all logic working with the normal X++ errors still applies. This is important – you can start using these custom exceptions without worrying that they would stop being handled in existing code.

    The complete source code (with examples) can be found on GitHub. It’s under MIT license, therefore you can do virtually anything with it, such as modifying it and including it in your commercial, closed-source solutions.


    0 0

    Reports offer Microsoft Dynamics 365/CRM USers a way to take data in CRM and slice and dice it within their CRM environment.

    In a recent Ledgeview Partners Microsoft Dynamics 365/CRM User Group webinar, we covered this specific data analysis method, but since this is just one data analysis method in Microsoft Dynamics 365/CRM, we value the opportunity to go over the various types that exist and when and when not to use them.

    This blog post will help give you the clarity you need when it comes to data analysis methods in Microsoft Dynamics 365/CRM.

    There’s a lot of data out there in your CRM system, and many ways to analyze it. Believe us – we know! It can be overwhelming, but when you are aware of the different methods and when and when not to use them, things become smoother.

    This chart will help you keep things straight when it comes to data analysis within your Microsoft Dynamics 365/CRM system.


    Do you need more support with your Microsoft Dynamics 365/CRM system? Contact Ledgeview’s CRM Support team. We are here to help provide the guidance you need to thrive from ongoing training, support, and customization. Keep your CRM system, education, and awareness current with Ledgeview.

    Learn more about Reports and various Data Analysis methods when you watch Ledgeview’s Microsoft Dynamics 365/CRM User Group Webinar on Reports.

    Watch it anytime on-demand here.

    Watch Webinar


    0 0

    Recently, while working on USD 4, we encountered one weird issue. After opening USD client, we selected O365 and provided credential to login. After selecting the instance to connect, USD client was...(read more)

    0 0

    Contributors: Michael Gernaey and Stan Ray The Microsoft Higher Education Accelerator is the second Industry Accelerator from Microsoft following the release of the Healthcare Accelerator earlier this...(read more)

    0 0

    In Part One of this topic we looked at using the manager field on a User to allow for filtering of data, and adding users to teams to make it easier to share views, charts and dashboards. What if we want...(read more)

    0 0

    Common Data Service

    Today’s fast and rapidly growing business organizations are on the lookout for a platform that has the potential to securely store and manage data used by business applications. Management of such intelligent business data is vital to make critical decisions around sales and marketing, accounts, and finance. For such requirements, the Common Data Service used by Dynamics 365 applications comes to the rescue. By enabling seamless sharing of business data to make efficient and informed business decisions with basic overhead, it enables organizations to have an integrated business environment. It provides out-of-the-box, intelligent business integration capabilities with a myriad of built-in features that eases the process of integration between business applications with very less or no custom code development, minimal risks, and ease of maintenance.

    Benefits of Common Data Service

    Common Data Service stores and manages data used by business applications within a set of entities or records and includes a base set of standard entities that cover typical scenarios. However, you can also create custom entities specific to your business and populate them with data using Power Query; you can then leverage PowerApps to build rich applications using this data. This secure and cloud-based storage option for your data offers several benefits:

    • Since both the metadata and data are stored in the cloud, it is easy to manage
    • Data is securely stored; role-based security ensures only authorized users have access
    • You get access to rich metadata and can leverage data types and relationships directly within PowerApps
    • You can define calculated fields, workflows, and business process flows to ensure data quality and drive business processes
    • Pre-defined business rules and logic ensure data consistency, irrespective of how users are accessing the data
    • Using add-ins for Microsoft Excel, you can increase productivity and ensure data accessibility

    Prospect to Cash Integration

    The Prospect to Cash Integration using Common Data Service provides a direct synchronization across Dynamics 365 for Finance and Operations, and Dynamics 365 for Sales. Templates available with the data integration feature enable the flow of data for accounts, contacts, products, sales quotations, sales orders, and sales invoices between Finance and Operations and Sales. By enabling data flow between Finance and Operations and Sales, you can:

    • Maintain accounts and contacts in Sales and sync them directly to Finance and Operations
    • Maintain products in Finance and Operations and sync them directly to Sales
    • Synchronize sales quotations, sales orders, and sales invoices between Sales and Finance and Operations

    Pre–requisite

    The only pre-requisite for enabling Prospect to Cash Integration is access to Common Data Service environment with Global Admin Role in Office 365 tenant with Dynamics 365 for Finance and Operations and Dynamics 365 for Sales.

    Steps for Integration

    1. Configure PowerApps settings

    • Go to https://portal.office.com/adminportal/home
    • Sign in with your Dynamics 365 for Sales credentials
    • From the menu, navigate to Purchase services. From the list of available services, select Microsoft PowerApps Plan2 – you can either purchase your plan or start with the free trial, which will be active for 3 months.
    • Activate the product license of PowerApps Plan 2.

    2. Create the Common Data Service environment

    • To create a new environment, go to Environment -> New Environment

    • Once the new environment form opens, provide the name and country region details specific to your organization. This will create a default Common Data Service database.
    • To set up the security for the newly created environment, go to Environments -> security and set the environment roles, user roles, and permission sets as per the needs of your organization.

    3. Set up Connections and Connection sets

    Connections are used to store Active Directory credentials of source/target applications whereas Connection sets are used to store organizational mappings. For example, legal entities in the case of Dynamics 365 Finance and Operations and sales units/organization in the case of Dynamics 365 for Sales.

    • To create Connections, go to PowerApps -> Home -> Data -> Connections

    • To create Connection sets, go to Admin center -> Data integration -> Connections Sets -> New Connection Set
    • Once the form is generated, fill in the connection set name, environment details, and sales unit/organization of both the environments.

    4. Create the Data Integration project

    You can create your own PowerApps projects, and correlate the source and target entities to enable a custom solution for integration and data management. You get the flexibility of field mapping, using the standard set of fields for every template listed in project creation. You can also schedule process synchronization manually or automatically with custom time interval and monitor the error and success charts of the integration procedure taking place.

    • For creating projects, go to Admin Center -> Data Integration -> Project -> New Projects

    • In the project wizard, provide the name for the project. Also, select a suitable template from the list of available templates for your specific business needs (for e.g. Sales accounts, Finance and Operations Customers, Sales Contacts, and Finance and Operations Common Data Service contacts.
    • Next, choose the connection sets and organizational mapping and click on Create to create a PowerApps project with standard mappings.

    • To view the standard mapping of the entities provided by the template, click MAP -> and dig into the mappings. You can also provide your own mappings if needed.
    • Save your project after any change.
    • Click on the run command to manually trigger the synchronizations for your entities.

    • You can also automate the synchronization of data integration project through the scheduling feature. To monitor the flow, the scheduler will automatically be triggered at regular intervals. For this, go to Data Integration -> Projects -> Scheduling

    • Running the project will integrate the entities both ways. You can monitor success logs as well as error logs.

    Streamline Operations

    The Azure-based storage facilitating the data storage centrally from various Dynamics 365 applications, Common Data Service makes it easier for you to store, maintain, and share data between different business applications. Using the Data Integrator tool, you can structure the end-to-end view of business data between the source application to the destination application with the help of Connections and Connection Sets. The Prospect to Cash Integration enables direct synchronization between Dynamics 365 Finance and Operations and Sales. Through this integration, you can seamlessly maintain and manage accounts, products, contacts, quotations, invoices, and sales invoices between the two applications and streamline operations across your business.


    About the Author - Angna Thakkar

    Angna Thakkar is a competent Senior Project Manager, Microsoft Dynamics AX Technical at Indusa with over 10 years of experience in managing multi-disciplinary teams of varying sizes and complex programs of work. She is always committed to professionalism, highly organized, able to see the big picture while paying attention to small details.

    Contributing Author:Malavika Nityanandam



    0 0

    Workspaces and functions: People . In this workspace you can search and find information on workers in your organization. You can see who reports to whom, and information about each employee. ...(read more)

    0 0

    Following are few keyboard shortcuts we can use in business central while transacting. General Alt+Q Open Tell me Alt+Up Open tooltip or validation error Tab Move focus to the next control Shift+Tab Move focus to the...(read more)

    0 0

    Whether your weapons are JavaScript and Plugins, or Processes and Flows,  there is a tool you should pick up before going anywhere near the keyboard. That is, of course, the pen.

    This is a lesson I learned while at university with my computing lecturer insisting we write out our code before committing it to the screen. Our major assignment was to code a token ring network controller. It might have been tough to write out every line of Pascal to make it work but when I finally entered it into the computer, the entire thing was bug free. The time taken to write it out and think it through calmly and carefully paid dividends in not having to debug my otherwise incoherent, spaghetti code.

    While I do not write every Workflow out in full before logging in to Dynamics, for the more complex ones there is a lot to be said for organising your thoughts on paper first. My general rule of thumb is if I cannot contain whatever it is I am developing on the screen (almost impossible for all but the most simple Flows), I write it out first. By going to a high level pseudo-version, I can see the algorithm on one page and usually improve my vision or discover issues which may not have been as visible in the weeds.

    Often coders will lament that their non-coding associates do not have good habits when developing. For me this is the first good habit of any developer. The pen is mightier than the DWORD.


    0 0

    Microsoft Dynamics GPMicrosoft Dynamics GP 2018 R2 was released on the 2nd October. In this series of posts, I’ll be going hands on and installing the majority of the components; some of them, such as Analysis Cubes for Excel, which are little used, I won’t be covering.

    The series index will automatically update as posts go-live in this series.

    The next of the additional products I am going to install, is the GP OData Service; this allows external tools, such as PowerBI, to connect to Dynamics GP.

    Launch the setup utility and, under Additional Products, select GP OData Service:

    Setup utility

    Accept the terms of the License Agreement and click Next:

    License Agreement

    Enter the full SQL Server Instance Name and the Dynamics GP System Database name and click Next:

    SQL Connection Information

    There is a few settings for the OData Service which need to be configured.

    The port will default to 443, but can be changed.

    The certificate is required, as are the logon credentials for the domain account which will run the OData Service.

    Once all fields have been entered, click Next:

    OData Service

    Click Install to begin installing OData:

    Ready to Install

    Once the installation is complete, click Exit:

    Installation Complete

    Click to show/hide the Hands On with Microsoft Dynamics GP 2018 R2 Series Index

    Read original post Hands On with Microsoft Dynamics GP 2018 R2: Install GP OData Service at azurecurve|Ramblings of a Dynamics GP Consultant


older | 1 | .... | 1101 | 1102 | (Page 1103) | 1104 | 1105 | .... | 1174 | newer