Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shift opens. In this blog we shall see how to close the blind shift. Steps: 1. Login to the POS 2. Open a new shift or continue with the existing one. 3. Click on Show blind closed shifts. 4. Select the shift you want to close. 5. At the bottom click on declare. 6. Declare the starting amount and the tender amount. 7. Click on close shift. This is how blind shifts can be closed.

Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filters in the Power BI service. All Power BI reports will now automatically retain the filters, slicers, and other data view changes that you have made. You no longer need to spend your valuable time slicing and dicing your report and repeating the same steps each time you return to the service. With this feature, you will be able to pick up right where you left off last time and quickly get to your insights! Also, if you want to reset all the filter to the state when the report was publishing, this feature will allow you to do that. Enabling Persistent Filter: To see persistent filters in action, simply head to any Power BI report that you have view or edit access to. You will notice a new button on the top bar that says, “Reset to default”. By default, this is disabled. It essentially means that you are viewing the author’s published view of the report and have not made any changes. Once you have modified the report to the view that you like, will activate the Result to default button, and will allow you to go back to default state when it was published. Click on reset to default And you are done.  Report will be reset to the default published state. Disabling persistent Filter for report: Persistent filter is turned on by default for all reports. If you want to disable the feature for the report, then you need to use the latest power BI desktop version that is released on Feb 2018. You need to navigate to : Power BI Desktop > Options > Report Settings > Persistent Filter. This is amazing feature that allows users to interact with report as they want. Try it out and let us know if there is any issue in comments below.

Issue: Microsoft Message Queuing (MSMQ) service running on Server might be unable to receive messages. Therefore, messages stay in “Waiting to connect” state in the outgoing queue of the sending computers. Cause: Issue occurs on 2 scenarios- During computer start, MSMQ service tries to bind to machine IP for listening which is still not acquired by DHCP. This might happen when DHCP takes some time acquiring IP due to any network latency or service start timing between DHCP and MSMQ. In this case MSMQ starts listening to the loopback address i.e. 127.0.0.1. DHCP acquired IP correctly and MSMQ listening on that IP as well. However, at some later point, DHCP IP renewal happens and now machine IP is different from the last one. In this case MSMQ is still listening on the older IP. So, when a new message comes for any old IP, it is never seen by MSMQ service. Verify Scenario: In Command Prompt, type following command and check the result netstat –abno | findstr 1801 If the system is facing this problem, output resembles the following in first scenario: TCP 127.0.0.1:1801 0.0.0.0:0 LISTENING xxxx TCP [::1]:1801 [::]:0 LISTENING xxxx Output resembles the following in second scenario: TCP y.y.y.y:1801 0.0.0.0:0 LISTENING xxxx where, y.y.y.y is the IP address which MSMQ port is listening to but this is different from the IP it should listen to. Resolution: Restart Message Queuing Service If Point 1 don’t resolve the issue, Install this Metadata hotfix.  https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2554746&kbln=en-US

Overview: Often, we wonder what could be wrong where we see a generic error on Documents in Dynamics 365. Something like this – That’s when you wonder if all the privileges in D365 Security Roles for SharePoint Site or Document entity are correct or not? In fact, it’s the SharePoint privileges that you must look into. Privileges On SharePoint: Even if the error indicates that you don’t have access in D365, it is actually the SharePoint site that’s missing permissions. Here’ where you need to check for the O365 User’s SharePoint privileges: Navigate to SharePoint Admin Center in the Office 365 Admin center Next, in any of the intended SharePoint sites, navigate to the Gear Icon and then Site Settings. In Site Settings, navigate to People and groups under Users and Permissions area. Check that you might not have the intended user in that list. You can then click on Add and add the user in the list. You can either add an individual user or ‘Everyone Except external users’. and confirm that you see them in the list now. Confirm Permissions: Now, you can ask the users to check and they should be good to go. Hope this helps!

Introduction: Html web resources are not loading properly on tablet version of Dynamics 365 sales. Description: We were working on custom html page which needs to be shown on tablet version of Dynamics 365. After the completion of development, we start testing. During testing some time html page was loading properly and sometime not. We thought this might be due to current changes in the customization. After, development was completed we start getting loading issue and we could not find why we are not able to load the form. We tried various approach to resolve this issue but we were not able to find the exact cause of not loading the html page on the tablet version. We noticed that this weird behaviours start coming when there is any customization done at CRM level. We also noticed that if you uninstall and reinstall the app it starts working fine but this is not a feasible solution to work every time to install and uninstall the app. Solution: We registered this case with Microsoft and we also tried every possible solution to work on this but this was still not resolving. Microsoft internally tried to replicate the issue and they said that- “Based on our investigation result, The root cause of this issue is that ‘this.LoadFinished();’ under CustomEventHandlersManager.cs is not being done when reproducing, hence the iframe would not be able to load. We have two ways you could try to resolve the issue: Option 1: Try to make form dirty and publish it again through form editor. The way we could make it dirty could be ‘Add a hidden field’, ‘Switch any two field like name and owner, then switch back’ Option 2: Other then way 1, user could visit any linked field on the form, like Owner, lookup field, then navigate back through top left navigation button If we go to option 2 and open another form, then it will hit loadFinished, when come back, the iframe loads well. The CustomScriptsContainerViewModel libraryNames not loaded are [“msdyn_/libraries/require/require.js”, “SystemUser_main_system_library.js”] Static names are [“/_static/_common/scripts/BusinessRulesExecution.js”,”_static/_common/scripts/BusinessRuleExecution.js”] So finally, 2nd approached work for me. This is still and open case with Microsoft. Conclusion: Hope this may help those who are facing the issue of HTML page loading on Tablet App on Android/iPad. I will update this post if I get a solution from Microsoft.

Introduction: This blog explains how to configure SLA to Work Order Entity. Scenario: Most clients demand SLA for Work Orders and Resource Bookings in Field Service. Steps of Implementation: We need to configure SLA for Work  Order as explained below. 1. Mark checked  for setting “Enable for SLA” on Work Order entity as highlighted below. 2. Create new Lookup Field with target record type as “SLA KPI Instance “as shown below. 3. Set the field on the form and insert the Quick View form as shown below also publish the cusotmizations. 4. Insert the “Quick View form” which shows time for First Response Lookup as shown below and pubish the Customizations. 5. Create a new record of SLA by navigating to Settings > Service Management > Service Level Agreements. 6. Create new record of SLA Details with below settings as shown below Select First Response In for SLA KPI field. Select criteria for SLA trigger time in “Applicable When”. Select criteria for SLA succerss in “Success Criteria”. Select criteria for SLA failure in “SLA Item Failure”. 7. Activate the SLA and “SET AS DEFAULT” button on the SLA ribbon form. Before enabling :- After enabling :- 8. Create a new record of Work Order and save it you will see SLA records shows the details. Conclusion: This blog explains how SLA can be configured to Field Service entities where it helps in tracking time by users on task.

Introduction: In this blog, I will outline how to migrate Email Attachments and update the status if an email. In my previous blogs, I have shown how to migrate the body of an Email and its Activity Parties from one CRM to another using Scribe. Email Attachments: Below, is the map used to migrate Email Attachments. As you can see, it is pretty straightforward, barring a few things to keep in mind while mapping. 1) Email Attachments are stored in the ‘activitymimeattachment’ entity. 2) I did not map the ‘attachmentid’ field as it produced an error as well as there is probably no reason one would need the GUID of the attachment. Not mapping attachmentid will create a new GUID for the attachments being migrated. 3) Most data regarding the Attachments migrated along with the first map migrating ‘Email’ activity. 4) That is why, in this map, we just migrate the subject, filename and body fields along with ‘objectid’ and ‘objecttypecode’. 5) The ‘objecttypecode’ tells which entity the attachment belongs to and its GUID. Once you run the map successfully, you will see the attachments displayed in the email. This includes image attachments as well. Target: Email Status Update: As for most Activity entities, while migrating, we migrate with an ‘Open’ status. This is done to ensure the record does not become read-only which would not allow us to migrate the corresponding Activity Parties and Attachments. This could lead to an inconsistency in data in Source and Target. Once the Activity Parties and Attachments have been migrated to the record, we can now update the Status of the Email to what it is in the Source environment. This is a basic but fundamental step to ensure no data inconsistency. Sample State Code & Status Code Values: In this map, all we have to map are the ‘Status Code’ and ‘State Code’ as it is in the Source Environment. This will update the status of the email. In the screenshot below, you can see that the Status has been updated to ‘Sent’. Conclusion: This completes the process of creating TIBCO Cloud Integration Maps for Email Migration from CRM to another. I hope this and my two preceding blogs provide a sufficient outline for the process of Email Migration.

Introduction: In this blog we will be discussing about marketing segments in Dynamics 365 for Marketing Preview.Marketing is basically promoting some products or services which an individual or organization has to offer. While marketing the main aim to decide a target audience. Once the audience is know,  the marketing content can be tailored to target that specific group of people. A market segment is the collection of contacts that you target in a marketing campaign. There are three types of segments a follows: Static Dynamic Compound Implementation: Static Segments: Members in the static segments are added explicitly. These members can be added by the marketer based on the personal interaction that he/she had with the customer. Step 1: Here we created a new static segment in the definitions tab we select the members using the check box as shown below. Initially the segment is in the Draft state. A point to be noted is that segment names can’t have blank spaces.   Step 2: Then we save and click the Check for Error on the top ribbon which validates the changes done as shown Step 3: After the validation is passed successfully we can click the Go Live button on the top of the ribbon. Dynamic Segments: The members in dynamic segment keep on changing based on the criteria that is setup. Every time a new contact is added to the system and it fulfills the condition specified in the query, it gets added to the dynamic segment. Step 1: In the designer at the bottom of the page we can see the total segment size which is the total number of members who will be added in the segment. In dynamic segments we design rules using the Designer or Flow or Query. Once we design the view using the designer we can see in the Query tab the query is populated. There are three operators that can be used is, is not and contains. Compound Segments: The third and final type of segment is the compound segment.Compound segments make use of static and dynamic segments which are live. As seen in the image below first we have to select the segment from the drop down and only the segments that are live will appear in the drop down list. Once the segment is selected we click on the arrow and then select one of Union/Exclude/Intersect. Finally, we see at the top of each segment how many members are included or excluded. Conclusion: These segments are used in customer journeys when we want to send marketing emails to a particular group of people.

Introduction: This blog explains how to Pause SLA in Dynamics 365. Steps to be followed: Only Enhanced SLA can be Paused. Go to Settings –> Administration  –> System Settings –> Service Select the Entity for which SLA is Created. (I have Created SLA for Word Order so I will select Word Order from that list). Now from Available Values select that Status that will Pause SLA. For Work Order entity we will create new Status as “On Hold”. (because it does not have any status which we can use to Pause SLA) Save and Publish. Now Select “On Hold”. Go to Work Order entity and select the Status = ‘On hold’ and Save. SLA is Paused now.

Introduction: In this blog you will see how you can use power BI as existing dataset to create the report in Power BI desktop. Service Live Connection: You can establish connection to a shared dataset in the Power BI service, and create many different reports from the same dataset. This means you can create your perfect data model in Power BI Desktop, publish it to the Power BI service, then you and others can create multiple different reports (in separate. pbix files) from that same, common data model. This feature is called Power BI service Live connection. To create Shared data set you need to, create a dataset and report and publish it in a workspace which is common to all. Select the workspace that is shared and where the report needs to be deployed. Report will start to Puclish to workspace. You will get below confirmation, when the report is sucecssfully published. Establish a Power BI service live connection to the published dataset If you’re not signed in to Power BI, you’ll be prompted to do so. Once logged in, you’re presented with a window that shows which workspaces you’re a member of, and you can select which workspace contains the dataset to which you want to establish a Power BI service live connection. Click on load and the dataset will be loaded and you can create the reports and publish it. Below are some known limitations to this as well: Read-only members of a workspace cannot connect to datasets from Power BI Desktop. Only users who are part of the same Power BI service workspace can connect to a published dataset using the Power BI service live connection. Users can (and often do) belong to more than one workspace. Try it out and put you question below if there is anything.