In this blog article, I will explain about the new updates of Power BI related to New Quick Calcs, Word wrap on matrix row headers and X-axis & Y-axis font size control. New Quick Calcs: Percent of row total & percent of column total In this Power BI update, they are introducing two new Quick Calcs. These are as follows: Percent of row total Percent of column total Under the field pane -> right click on value field -> Quick Calc. Then, under Show value as, you will see Percent of column total and Percent of row total If you convert a matrix visual with one of these new Quick Calcs, the calculation will convert these totals into a percent of grand total. Example: In below figure Cost column shows the cost for sub category. After applying the Quick Calcs as Percent of column total the matrix is looks like follows: Word wrap on matrix row headers: In earlier update, the word wrap was added for table header only but now it’s added for matrix row header as well. You will see the Word wrap toggle under the Formatting pane -> Row header card -> Word wrap. Once you turn on word wrap, the row headers will word wrap to fill the space they have. X-axis and Y-axis font size control Earlier we were not able to control the font size of X-axis and Y-axis. But now we can control the X-axis and Y-axis font size. Now you can find the text size slider under the X- axis and Y- axis card in the formatting pane. After changing in font size of X- axis and Y-axis.  

Overview: You’ve been using Dynamics CRM 365 for your organization. And there is a need to make the information stored in your D365 accessible to your customers in a user-friendly interface. That’s where Microsoft CRM Portals come into play! Previously owned by ADX Portal, D365 Portals are now available Online. With each D365 Plan 1 Business Application subscription, 1 Portal Add-On is provided for free. Users can access portals by signing into the Portal. Users are stored in Dynamics 365 in the form of Contacts. Customers are invited to the Portals by Invitation method. Upon creating and account / redeeming an invitation, they can manage their own profile. Setting Up Portals You can setup Portals from the Office 365 Admin centre. Here is how you can do that: Navigate to the Admin area in Office 365 and on the left-hand pane, scroll down and expand Admin section. In the D365 Admin area, select the instance you want to enable the Portal on and click Solutions. (The same can also be installed from the Applications tab in the Dynamics 365 Administration Center.) Once inside solutions, select the Portal you want to deploy for your organization. It takes about a few minutes to install. Once this is installed, you can check the Applications tab and the Portal installed will appear there for you to manage. All the Portal actions can be administered from here (Manage option). Sample Customer Self Service Portal: Types of Dynamics 365 portal There are 4 types of Portals that could be setup using the free add-on with each D365 Plan 1 subscription: Custom Portal Custom Portals come with minimal set of pre-defined page templates where you can start creating a Portal of your own per your tailored needs. Customer Self-Service Portal Customer Self Service Portal is used by the customers of the organization. This portal is their own space of use where they can login and view as well as register their own support cases and manage the same. Along with that, Knowledge Base can be accessed and Forums topics can be started on this portal. Partner Portal Partner Portal enable business partner to build business by working on Opportunities of your organization. Community Portal Community Portal serves to grow a community of people by sharing ideas, voting them and starting forum discussions about a certain topic.

Dynamics 365 for finance and operations which is earlier known as Dynamics AX is nothing but Microsoft’s flagship ERP solution. Small, medium and large companies can use this ERP suite to become efficient and to streamline their processes. It is an application that helps companies stay flexible. There are so many excellent features in this particular software that will help users become a lot more efficient than they were before.  Since it is a cloud-based, and all the changes that occur in it are real-time. Teams can work with team members that are working across the world with ease. New users might struggle with a few aspects such as creating service orders from the sales order when they are using X++. In this blog article, we will see how we can create Service Order from Sales Order using X++ in Dynamics 365 Operations. I have created a button in Sales Order form which will run a class (MenuItem – Action) to create Service Order Header. Create a new Class: class CFSServiceOrderCreateFromSalesOrder { SMAServiceOrderTable serviceOrderTable; SMAServiceOrderLine serviceOrderLine; SMAserviceTaskRelation serviceTaskRelation; SalesTable salesTable; } Create a main method: public static void main(Args _args) { Args serviceOrderTableArgs = new Args(); CFSServiceOrderCreateFromSalesOrder serviceOrderCreateFromSalesOrder = CFSServiceOrderCreateFromSalesOrder::construct(); ttsbegin; //Call to method createSMAServiceOrder() for Service Order Header creation serviceOrderTable = serviceOrderCreateFromSalesOrder.createSMAServiceOrder(_args.record()); ttscommit; //Infolog to display service order id if service order created else failure message if(serviceOrderTable) info(strFmt(“ServiceOrderHeader created with ID: %1”, serviceOrderTable.ServiceOrderId)); else info(“ServiceOrderHeader creation failed”); } Create SMAServiceOrder() method: This method is used to create a Service Order header record. public SMAServiceOrderTable createSMAServiceOrder(SalesLine _salesLine) { //initialize SMAServiceOrderTable serviceOrderTable.initvalue(); //Initialize Service Order ID NumberSeq NumberSeq; NumberSeq = NumberSeq::newGetNum(SMAParameters::numRefServiceOrderId(),true); serviceOrderTable.ServiceOrderId = NumberSeq.num(); serviceOrderTable.CustAccount = _salesLine.custAccount; serviceOrderTable.ProjId = _salesLine.ProjID; //display Customer Name as Service Order Description serviceOrderTable.Description = CustTable::find(_salesLine.CustAccount).name(); //insert Service Address serviceOrderTable.updateCustAddress(); serviceOrderTable.insert(); return serviceOrderTable; } So, this will create a Service Order Header from Sales Order. Let me know your reviews. I will soon come up with more articles, as I further explore D365 Operations.  

Dynamics 365 for finance and operations is a product from Microsoft. It is an ERP or enterprise resource planning software. Both medium and large companies can benefit from using this ERP solution. Companies can streamline the processes in the finance and operations functions. You will get a detailed view of what’s happening in departments such as warehousing, manufacturing, finance, budget planning, IT, demand forecasting and transportation to name a few.  It is very easy to install and use this ERP solution. But, if you are a new user, you might struggle initially as you do not know how to operate the system and to get what you want on it. For example, you might not know how to import the budget using excel in this application. Dynamics 365 for Financials has a feature of defining Budgets for chart of accounts. The budgets can be defined in a multiple combination using dimensions and periods. Generally, companies have a huge list of Chart of Accounts and it becomes difficult to create budget for each chart of accounts in the system. Thus, Microsoft has provided a tool to import budgets in Dynamics 365 for Financials using Excel. Following are the steps to import budgets: In the global search, search for G/L budgets and click on it. Click on new to create a new budget. Provide a name & description to the budget and then click on Edit budget. Once the budget is created, go to Action tab and click on Export to Excel. On clicking of Export to excel, system will ask for Start date, No. of periods in budget and Period length. This data will be useful to design the budgets. (For e.g. Starting from 1st February 2017 I need to create a two-monthly budget for petty cash, then I will select start date as 01/02/2017, no. of period would be 2 and period length would be 2M). Once OK is clicked, an excel file will be downloaded in the system. Open the excel file and put the amount against the respective ledger and save the file. Once the file is saved, click on Import from Excel in the Action tab. The system will ask the Budget name which will be the newly created budget. There are two options available either to replace entries if there are any entries created previously or to add new entries if the user needs to append already created budget. On clicking of OK, the system will ask the path where the excel file is stored. After providing the path system will automatically either replace or add entries to the budget (depending on the option selected). Conclusion D365 for financials is a very good product for Small and medium size enterprises. The import budget features can become a very effective tool to design complicated budgets in the system within very less time.  

In this blog article, I will explain you on the new web part which enables SharePoint authors to embed Power BI reports directly in SharePoint Online pages with no code required. Below are the steps to connect over SharePoint Online: Publish your Power BI report to your Power BI account Get the URL to the report Add the Power BI (preview) web part to your SharePoint Online page Paste the URL of the report when prompted To finish, save and publish your page! As per below screenshot I have one Reports publish on my Power BI account, so at report level in the File menu we need to select “Embedded in SharePoint Online” option. One Pop-up window appear for the URL which we need to copy for the SharePoint online site. Now login to your company SharePoint Online account. And create new page inside of existing Page or Separately. As per below screen shot click on “+” sign and select Power BI option, after clicking new report window appears. So, when you click on Add Report button, you found one window appears on left side where you need to paste that powerbi URL inside of first block. And it will automatically detect all the reports related to that Power BI account. Power BI reports appears inside of SharePoint Online account as below. You can also share the same Reports to other colleagues inside of organization.  

Companies that want to become efficient should choose to adopt an ERP solution into their systems. Only then they can provide the best customer experience to their valuable clients. Microsoft Dynamics NAV is an enterprise resource planning application that helps companies to not only become efficient but to successfully mitigate losses. Once, you select the package, the ERP system providers will come and install the software and provide the necessary training to your staff so that they work efficiently.  New users will take some time before they get used to the system. Doing certain tasks might seem to be difficult in the beginning. For example, creating a new database in NAV 2017 might seem like a mammoth task. Here are details of how you can do it.  Introduction: Generally, when we install NAV, a default Demo database is always created in the Microsoft Dynamics NAV Development environment. In this blog, a new database is created thus, the developer can use two or more databases in a single NAV Development environment. Pre-requisites 1. Microsoft Dynamics NAV Development Environment 2. Microsoft SQL Server Management Studio. Steps In the Microsoft Dynamics NAV Development environment, Click on file then database and New. A new window opens, enter the database name of your choice and then click on OK. This creates a database with limited number of table objects starting from number 2000000004 i.e Permission set. Here Upgradation Database is the name of the Database Open the Microsoft SQL Server Management Studio as Administrator, navigate to the Demo datebase then navigate to Tasks and select Backup A new window opens, and click on Add button to specify the backup path Click on the button highlighted in the above screenshot, a new window opens, locate the database file and specify the file name and then ok. This will take the backup of the specified database. Now go to the new database created, in this example the database name is ‘Upgradation Database’. Navigate to task then restore then database. Now select device radio button in the source, click on the Assit edit button. Select the folder and select type as All Files. Select the Option and check the overwrite and close existing connection to destination database and then click on OK. Thus, using the above given steps a new database is created with all the standard objects. To access this database from the front end we need to create a server instance in Dynamics NAV Administrator and link it to the newly created database. In the Microsoft dynamics NAV Administrator, right click on the Microsoft dynamics NAV(Local) and select Add Instance. Here Specify the Server Instance name and enter the unique port numbers and click on OK. This creates the server instance. Now to link it to the database, click on the server instance, click on the edit button and scroll to Database fast tab. Specify the Database name and click on save. Now Click on stop and start the services for the Microsoft Dynamics NAV server instance. Open Microsoft Dynamics NAV 2017 front end and click on select server and specify the server instance address and click on tab, the available companies will be displayed then click on OK.  

Microsoft Dynamics 365 for Retail Management Solution is one of the best and popular ERP cloud solutions. It is a lot efficient and effective than a lot of other similar products that you can now find in the market. Even in the peak hours of the day, you can give the best customer experience to your clients. And the best part is that you can achieve this without gaps or duplication. It is one of the main reasons why a lot of business people rely on this ERP solution. It is easy to install and use this app.  However, if you are a new user, you might find it a little difficult to manage this application. Here’s how you should handle AX retail POS error. Introduction: In AX Retail POS, the Implementation Administrator created a new Windows user ID. But new user trying to open the Retail POS, he is getting error “Retail POS Cannot connect to a database. Try again Later or see your system administrator. “.  As we all know for the online store required the Store channel database and store Massage database. The system administrator created this database from the Administrator user ID or Administrator Permission. But still this Error occurred? Error: Why this error occurred? Answer:  Store channel is the database where all retail POS transaction data stored Like ( sales Transaction, shift details, POS profile, store and terminal details…etc.).  User ID can to connected to this Database or user ID does available for store channel database in SQL. Because of this reason when new user tries to run the Retail POS application, he gets this error message. How to solve this issue? Follow the below steps: Login Point of Sales system from administrator. Then Open the store SQL server. After opening SQL, In Object Explorer go to Security -> logins Right Click on Logins and select New Login option In the General tab, select the Windows authentication option and after that click on the Search button. Add the new user ID. <Domain Name>\<New User ID> (Note:- Make sure that your system should be in the domain while adding new user). For demo use, I am using my domain CloudFronts\Amol Select User Mapping Page, In User Mapping Page Map Store Channel Database and Store message database. Select Database Role membership for Store channel database and store message Database. Role should be db_accessadmin, db_datareader, db_datawriter, db_excutore and click on OK button. Restart the Async client Service and run the Retail POS. Conclusion: Adding User with permission in SQL for Store channel database and Store Message Database, allow windows users to interact with the database from Retail POS application.  

In this article, we are going to see how to configure CSV file as source in TIBCO Cloud Integration. Prerequisite: TIBCO Cloud Integration Subscription. CSV file (Here, Journal.csv) Steps: Provide access to your Text files. The FolderAccess.txt file controls access to the files that can be opened by TIBCO Cloud Integration or processing. Open the FolderAccess.txt file in Notepad. Location for FolderAccess.txt: Here: C:\Program Files (x86)\Scribe Software\TIBCO Cloud IntegrationAgent\Connectors\Scribe.Connector.Text Add a line in the FolderAccess.txt file for each directory path that contains text files. Open ODBC Data Source Administrator. In the System DSN tab, add a driver of Microsoft Access Text driver Add Data Source name and description. Select directory where your CSV file is stored. ‘Save as ‘the .CSV file as schema.ini file. Login to TIBCO Cloud Integration URL: https://app.scribesoft.com/ Create a new connection by selecting the connector type as Text as Source. Fill in the required details. In the Location Tab, paste the path where your .csv file is stored. In the Entities tab, give the entity name and fill the details. In the Fields tab, click on settings icon and Refresh schema. All the fields in the CSV file will appear. The data type of all fields are by default ‘Text’, you can change the datatype of the fields. Test the Connection and press ‘OK’ to save the connection.

ERP stands for Enterprise Resource Planning. So many companies are developing ERP software to streamline the processes. Dynamics 365 is one of the ERPs that will help the companies scale up high swiftly. You need to work with the best ERP system providers like CloudFronts if you want this software to make a difference in the lives of people.  Microsoft Dynamics Nav is an ERP app that is developed by Microsoft. It is very much part of the popular Microsoft Dynamics family. Companies that use this product can streamline departments such as manufacturing, electronic commerce, supply chains, customer relationship management and so forth. Small and medium-sized companies are going to benefit greatly when they use this software.  Here is a segment that you should know in this ERP application. Introduction: Upgradation of objects/data in NAV have to be done after the application has been upgraded to the latest version. Code from different versions of NAV application have to be merged to upgrade the data. This process of merging objects in NAV between different versions is known as code/data upgradation. Pre-requisite: Microsoft Dynamics NAV Windows PowerShell ISE The following objects have to be exported and saved: All Standard objects of the previous version of Microsoft Dynamics NAV in .txt format. All objects of the modified database of Microsoft Dynamics NAV in .txt format. All Standard objects of the higher version of Microsoft Dynamics NAV to which the objects have to be migrated in .txt format. After all these steps are performed, install the latest version of Microsoft Dynamics NAV to which objects need to be migrated. Purpose: The main purpose of Data Upgradation is to move customizations done in any previous version of Microsoft Dynamics NAV to the new Higher version of Microsoft Dynamics NAV database. Steps: Create 4 folders i.e. Original, Modified, Result and Target in the system. Fig 1: Create four folders as specified above Save the backup of ‘All Standard objects of the previous version of Microsoft Dynamics NAV in .txt format’ in the Original Save the backup of ‘All objects of the modified database of Microsoft Dynamics NAV in .txt format’ in the Result Save the backup of ‘All Standard objects of the higher version of Microsoft Dynamics NAV to which the objects have to be migrated in .txt format’ in the Target Open Windows PowerShell ISE as administrator. Run the following commands in it and refresh PowerShell. Import-Module “C:\Program Files\Microsoft Dynamics NAV\100\Service\NavAdminTool.ps1” Import-Module “C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\NavModelTools.ps1” These commands help to load Dynamics NAV Cmdlets into the runspace. Fig 2: Windows Powershell ISE commands to load Microsoft Dynamics NAV Cmdlets In Windows Powershell ISE, go to Merge-NAVApplicationObject Cmdlet and enter the path of the four folders created initially i.e. Original, Modified, Result and Target folder. Fig 3: Merge-NAVApplicationObject Cmdlet Fig 4: Merge-NAVApplicationObject Cmdlet gives details of the merge process After running the Merge-NAVApplicationObject Cmdlet the Result folder will automatically be filled with all objects in .txt format. Each object file will be stored separately. Fig 5: Result folder contents Now, in order to create one .txt file by joining all the .txt files present in the Result folder, navigate to Join-NAVApplicationObjectFile Cmdlet in Windows PowerShell ISE. Enter the path of the Result folder as the Source and enter a name of the Destination as ‘Merge.txt’ Fig 6: Join-NAVApplicationObjectFile Cmdlet This will create Merge.txt file in the specified location. Fig 7: Merge.txt file created Now import the txt file into the new database of the Higher version of Microsoft Dynamics NAV. Errors if existing will be displayed during the import process and the import process will stop there. The errors have to then be rectified and the Upgradation process has to be repeated again from step 6. After all errors are rectified and conflicts are resolved, the Merge.txt will be successfully imported. Now, compile all the objects of the new database. You will have a new database with a fully application and data/code including all the modifications and customizations. Conclusion: Using the above process, modifications and customizations done in the previous version of Microsoft Dynamics NAV can be successfully migrated to the Higher version of Microsoft Dynamics NAV.  

Error in Scribe Insight: “Conversion failed when converting date and/or time from character string” when connected to SQL Adapter. When do we get this error? When we create a SQL connection using ODBC or OLEDB adapter in Scribe Insight and use the same either as Source or Target connection in Scribe DTS. What is the root cause of this error/issue? It’s the date-time format of the machine where the scribe Insight DTS is being run. How can we reproduce the error? In the windows, DateTime settings, change the format for time with separator as (.) instead of (:). Open the Scribe Workbench and create a sql connection using odbc\oledb connection, create a target connection, map some fields and run the DTS. You will get the error. Resolution: Simply change the time format to have the colon separator instead of (.) Hope this helps. I have found that having the time format other than colon separator creates error while working with other ETL tools as well.