Quantcast
Channel: Dynamics 365 Blog
Viewing all 678 articles
Browse latest View live
↧

Potential issues when installing 8.0.4 on the Tier II sandbox environment

September 21, 2018, 1:54 am
$
0
0

When installing cumulative update on 8.0.4 on Tier II sandbox environment you may experience the error:

“The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Unable to resolve dependency ‘dynamicsax-applicationfoundationformadaptor’.”

This due to the fact that there is a X++ code released in Demodatasuite model where we changed the class SalesOrdersCleanup.

On Tier II there are no Demodatasuite model or any related models installed and this is why we are getting error. The way to go is to exclude the model from the build definition https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/dev-tools/exclude-test-packages

↧
Search

Inspecting a D365FO Meta Data Hotfix Content

October 19, 2018, 12:52 am
$
0
0
In this article, you will find detailed instructions, on how to inspect content of a D365FO meta data hotfix. The article describes a manual approach as well as running PowerShell scripts to extract the underlying dependencies of hotfixes and affected objects. All descriptions are in attached “Inspecting a D365FO Meta Data Hotfix Content.docx” document. Inspecting-a-D365FO-Meta-Data-Hotfix-Content2... Read more
↧
↧

Extending the Extended Logon functionality for MPOS and Cloud POS

December 14, 2018, 8:44 am
$
0
0

Included in MPOS and CPOS are two methods for extended logon functionality: logging in by scanning a barcode or by swiping a card with a magnetic stripe reader (MSR). Setup for these are described here: https://docs.microsoft.com/en-us/dynamics365/unified-operations/retail/extended-logon.

One shortcoming of the out-of-the-box functionality, however, is that each of these methods only allows for five significant digits for a unique identifier. For example, if you have two cards with the IDs “1234567” and “1234578” you will find that they will be considered the same “12345” and the second card will fail when it is attempted to be assigned to an operator.

The reason for this problem is relatively simple: the implementation of the extended logon was originally intended to be a sample upon which developers could customize to fit the specific needs of a particular implementation. In prior versions of the product (going back to Dynamics AX 2012 R3) this was much easier since we shipped the full source code to the Commerce Runtime (CRT). However, because the CRT is now sealed, developers have to create a custom CRT service to override existing functionality – something that is difficult to do from scratch.

This blog post is an end-to-end sample that can be used as a starting point for such an implementation. It is intended as a specific workaround for the five-character limit for barcode and MSR scans, but does not discuss extending to other devices.

Here is a link to a zip file for the source code for the sample:  Contoso.ExtendedLogonSample

Architecture

There are essentially two main pieces to the functionality for barcode and MSR extended logon: assigning the identifier (barcode or card number) to the user and then creating a hook on the logon screen to act on the event of a cardswipe or barcode scan.

The following is a simplified explanation of the logon screen:  when the logon screen displays, MPOS automatically listens for one of the two events (a barcode scan or card swipe). If either of those events fires, instead of attempting to authenticate with an Operator ID and Password, the CRT logon request (UserLogOnServiceRequest ) is called with a special parameter.  This parameter, GrantType, notifies the CRT what kind of event was fired.   This, along with the actual text (card number or barcode) is used to perform the extended logon workflow instead of the standard workflow.

The second part of the functionality is the assigning the barcode or card number to the Operator ID. This process is similar and re-uses some of the same logic. On the Extended log on screen, the user searches for the Operator ID to which they will be adding an identifier (card number of barcode) and then swipes the card or scans the barcode. Pressing the OK button sends this identifier to the CRT which will then check to see if the identifier is already in use and if not, adds a record to a table to map the Operator ID and barcode or card number.

All of this is done with three CRT requests that you need to implement in your custom service: GetUserEnrollmentDetailsServiceRequest, GetUserAuthenticationCredentialIdServiceRequest, and ConfirmUserAuthenticationServiceRequest.

Notes on the Code

There are three requests that need to be handled by your custom code:

public IEnumerable<Type> SupportedRequestTypes
{
    get
    {
        return new[]
        {
            typeof(GetUserEnrollmentDetailsServiceRequest),
            typeof(GetUserAuthenticationCredentialIdServiceRequest),
            typeof(ConfirmUserAuthenticationServiceRequest)
        };
    }
}

public Response Execute(Request request)
{
    if (request == null)
    {
        throw new ArgumentNullException("request");
    }

    Response response;
    Type requestType = request.GetType();

    if (requestType == typeof(GetUserEnrollmentDetailsServiceRequest))
    {
        response = this.GetUserEnrollmentDetails((GetUserEnrollmentDetailsServiceRequest)request);
    }
    else if (requestType == typeof(GetUserAuthenticationCredentialIdServiceRequest))
    {
        response = this.GetUserAuthenticationCredentialId((GetUserAuthenticationCredentialIdServiceRequest)request);
    }
    else if (requestType == typeof(ConfirmUserAuthenticationServiceRequest))
    {
        response = this.ConfirmUserAuthentication((ConfirmUserAuthenticationServiceRequest)request);
    }
    else
    {
        throw new NotSupportedException(string.Format(CultureInfo.InvariantCulture, "Request '{0}' is not supported.", request));
    }

    return response;
}

GetUserAuthenticationCredentialIdServiceRequest and GetUserEnrollmentDetailsServiceRequest are very similar: each validates and returns the significant digits of the scanned barcode or swiped card. The first one is used during the logon process and the second one is used when assigning an extended identifier to an operator.

private GetUserAuthenticationCredentialIdServiceResponse GetUserAuthenticationCredentialId(GetUserAuthenticationCredentialIdServiceRequest request)
{
    return this.GetUserAuthenticationCredentialId(request.Credential, request.RequestContext);
}

private GetUserEnrollmentDetailsServiceResponse GetUserEnrollmentDetails(GetUserEnrollmentDetailsServiceRequest request)
{
    string credentialId = this.GetUserAuthenticationCredentialId(request.Credential, request.RequestContext).CredentialId;
    return new GetUserEnrollmentDetailsServiceResponse(credentialId, string.Empty);
}

Each of these shares the same validation method (GetUserAuthenticationCredentialId). This method operates on two pieces of information: the full string that was just scanned in (barcode or card number) and the current device configuration. It performs three validations and throws specific exceptions if any fail: is the device is even configured to use this type of extended logon (as defined in the functionality profile), whether a good swipe or scan was made, and whether the barcode or card number had enough characters.

If everything looks good, a GetUserAuthenticationCredentialIdServiceResponse with the identifier is returned to the caller. The caller (CRT and then ultimately MPOS) will handle the three exceptions appropriately.

Note that this is the method where the out-of-the-box implementation is hard-coded to only five characters. This sample requires a barcode of at least ten characters and only the first ten characters are stored in the database.

 

private GetUserAuthenticationCredentialIdServiceResponse GetUserAuthenticationCredentialId(string credential, RequestContext requestContext)
{
    DeviceConfiguration deviceConfiguration = requestContext.GetDeviceConfiguration();

    if (!this.IsServiceEnabled(deviceConfiguration))
    {
        throw new UserAuthenticationException(SecurityErrors.Microsoft_Dynamics_Commerce_Runtime_AuthenticationMethodDisabled, "Authentication service is disabled.");
    }

    if (string.IsNullOrWhiteSpace(credential))
    {
        throw new DataValidationException(DataValidationErrors.Microsoft_Dynamics_Commerce_Runtime_MissingParameter, "credential");
    }

    if (credential.Length < IdentifierLength)
    {
        throw new InsufficientCredentialLengthException(DataValidationErrors.Microsoft_Dynamics_Commerce_Runtime_InvalidFormat, credential.Length, IdentifierLength);
    }

    // Only use the first IdentifierLength (10) characters
    string credentialId = credential.Substring(0, IdentifierLength);
    return new GetUserAuthenticationCredentialIdServiceResponse(credentialId);

ConfirmUserAuthenticationServiceRequest: This request is the second stage of the logon process. At this point the extended identifier (card number or barcode) has been translated to an Operator ID (based on the mapping in the RetailStaffCredentialTable).

There are two scenarios that affect this request: whether the device is configured to challenge for a password after scanning or not. If the barcode or card swipe is enough (no password needed) then this request essentially does nothing; it returns a NullResponse object which is an indicator to MPOS that a successful logon was made.

However, if the device is configured to require a password, this request will get hit twice during the logon process.

The first pass happens before the user gets prompted for their password. In fact, the specific exception that gets thrown (Microsoft_Dynamics_Commerce_Runtime_PasswordRequired) is a signal to MPOS that it needs to prompt the user for a password. You may notice that this password entry dialog looks different than the standard login screen; it is actually a dialog box.

After the user enters the password, the ConfirmUserAuthenticationServiceRequest gets called a second time, this time with both an Operator ID and a password. The request then is responsible for calling the standard logon request (UserLogOnServiceRequest) before the user can gain access. If no exception is raised from that call, the NullResponse is again returned a successful logon. If an exception is raised (i.e., the password entered is incorrect) it will just bubble up to the caller and MPOS handles it just like if the user entered an incorrect password on the main logon screen.

private Response ConfirmUserAuthentication(ConfirmUserAuthenticationServiceRequest request)
{

    DeviceConfiguration deviceConfiguration = request.RequestContext.GetDeviceConfiguration();

    if (!this.IsServiceEnabled(deviceConfiguration))
    {
        throw new UserAuthenticationException(SecurityErrors.Microsoft_Dynamics_Commerce_Runtime_AuthenticationMethodDisabled, "Authentication service is disabled.");
    }

    if (this.IsPasswordRequired(deviceConfiguration))
    {
        if (string.IsNullOrWhiteSpace(request.Password))
        {
            throw new UserAuthenticationException(SecurityErrors.Microsoft_Dynamics_Commerce_Runtime_PasswordRequired);
        }

        // call auth service for password check
        UserLogOnServiceRequest passwordAuthenticationRequest = new UserLogOnServiceRequest(
            request.UserId,
            request.Password,
            request.Credential,
            PasswordGrantType,
            request.ExtraAuthenticationParameters);
        request.RequestContext.Execute<Response>(passwordAuthenticationRequest);
    }

    return new NullResponse();
}

Additional Notes

  • The class needs to implement a property named HandlerName.  These are specific identifiers for card swipe nd barcode and are hard-coded in the MPOS code.  Because of this, they are not easily changed and your implementation of either should just use the same hard-coded values.
public string HandlerName
{
    get
    {
        return "auth://example.auth.contoso.com/barcode";
    }
}
  • All of the data handling for the extended login information is taken care of behind the scenes.  When the user is assigned a barcode or card number, it calls Realtime Service to save the number to the RETAILSTAFFCREDENTIALTABLE at Headquarters and also to the local (channel) version of the table for immediate use.  Depending on how often you run CDX jobs, it will eventually also get pushed out to other stores as well.
  • To test your plugin, compile and deploy to Retail Server as noted in these instructions:  https://docs.microsoft.com/en-us/dynamics365/unified-operations/retail/dev-itpro/commerce-runtime-extensibility.  You will need to add the Extended log on operation to a button grid to be able to assign barcodes to a user.  The easiest way to test is to use the Barcode Scanner in the Virtual Peripherals tool – use “work as keyboard wedge” to avoid having to mess with OPOS drivers and hardware profiles.
↧

Renew Dynamics 365 for Finance and Operations Certificate on Dev Machine

December 27, 2018, 7:11 pm
$
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.

Symptom:

You will get error 503 when trying to access local URL https://usnconeboxax1aos.cloud.onebox.dynamics.com/

Check in Computer Certificates, you will see Certifcates started  with DeploymentsOnebox expired.

Workaround:

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.

↧

[AX2012] [Workflow approval via email] Migrate from ACS to SAS – troubleshooting

February 17, 2019, 4:14 am
$
0
0

Latest whitepaper & mobile connector downloading address –
https://mbs.microsoft.com/customersource/northamerica/AX/news-events/news/MSDYN_MobileAppsAX

When you migrate from ACS to SAS, you only need complete below 4 tasks listed in Appendix F: Apply the 2018 update to migrate from ACS to SAS.

1 Follow the steps in Appendix A: Create a new Service Bus namespace to create a new SAS Service Bus.

2 Follow the steps in Appendix B: Configure shared access policies, so that you can provide the key as the Azure service identity password in the connector parameters.

3 Install the latest connector, and update the Azure service namespace, Azure service identity name, and identity password from the previous steps.

Note: The latest connector is not backwards compatible with ACS. Once the latest update is applied it will no longer work with ACS. The previous ACS solution is set to be deprecated on Nov 7, 2018.

4 In AX 2012, In the Settings for workflow form, update the Base URL to approve/reject workflow field with the details of the new Service Bus.

 

This blog only focuses on some difficulties you might experience in item #1 when you create SAS service bus with the Azure power shell. When you follow the sample power shell commands in the Appendix A, you might run into some errors and cannot proceed. This blog also shows you some screenshots after you complete the configuration and test the feature with email approval.

Errors I faced when handling with Azure power shell

Install Azure power shell

This indicates the windows PowerShell version is too low to meet the minimum requirement for Azure PowerShell. You need to update it to at least 5.1 and then can proceed with Azure PowerShell installation

Login-AzureRMAccount

From below overview of Azure power shell, we know there are 2 modules for Azure power shell, meaning there are 2 different sets of Azure commands you can use to run the Azure power shell commands. Unfortunately, the white paper is using the AzureRM module and I was not able to go through successfully. Instead, Az module works well for me. So, I recommend you use Az module as well to proceed.  Az module is also recommended as you can see from below overview screenshot.

Use Connect-AzAccount instead to proceed.

Enter your Azure subscription account in below screen

Step 3 to check and select the Azure subscription ID.

Create the service bus with power shell command. Note you need to create the resource group manually on Azure portal before your run the command. Otherwise you will face below error. Note the diagram in whitepaper to elaborate this command is really confusing and sort of wrong.

Below is screenshot from whitepaper to elaborate the power shell commands to create service bus, however it’s using AzureRM and has some issue in particular with explanation of the parameters.

Below is my sample command I used to create my service bus. You can simply follow it to create your own service bus.

New-AzServiceBusNamespace -ResourceGroupName LeoResourceGroup20190115 -NamespaceName LeoServiceBus20190115 -Location ‘Southeast Asia’

It will take less than 1min to create the service bus with the Azure PS. Then you’ll get below output. Save it somewhere.

In summary, below is a mapping between the commands in the whitepaper and commands for Az module –

Orignal command in whitepaper Description Resolution/Sample commands in my lab
Install-Module -Name Az -AllowClobber Install Azure PS Check windows PS version. Make sure 5.1 at a minimum.
Login-AzureRmAccount Connect Azure PS with your Azure subscription Connect-AzAccount
Get-AzureRmSubscription learn the subscriptions that are available and then select one of them Get-AzSubscription
Select-AzureRmSubscription -SubscriptionId <“subscriptionId”> learn the subscriptions that are available and then select one of them Select-AzSubscription -SubscriptionId “your Azure subscription ID”
New-AzureRmServiceBusNamespace -ResourceGroupName <-resourceGroupName-> -NamespaceName <-serviceBusName-> -Location <-WestUS-> Create Service bus with Azure PS New-AzServiceBusNamespace -ResourceGroupName LeoResourceGroup20190115 -NamespaceName LeoServiceBus20190115 -Location ‘Southeast Asia’

 

Mobile connector

As of now (Feb 2019), version of the latest mobile connector is 8.2.387.0. Note – you always need to download the latest mobile connector from above link to configure this feature. Due to the topology change, old connector doesn’t support latest SAS.

Side notes for connector–

  1. Mobile connector doesn’t have to be installed in AOS servers. You can install it on any server you like. No AX component is required for mobile connector.
  2. If you run into below error when opening mobile connector UI, this is because the mobile connector service is in Stopped status. Simply start it from windows service list then you’ll be good to fix this issue and start the UI.

  1. ADFS is not required for workflow approval via email. So, you can enter any value when configuring parameters on connector UI for ADFS. Only 4 parameters as below are required for workflow approval via email. All rest you can just provide some dummy values for them.
    1. Azure service namespace – it’s the service bus name LeoServiceBus20190115
    2. Azure service identity name – use default sendlisten
    3. Azure service identity password – primary key in SB > SAS > Primary key
    4. Endpoint URI of EmailApprovalsServices – Just replace the placeholder which is the AOS name. Sample : net.tcp://DAX2012R3:8201/DynamicsAx/Services/EmailApprovalsServices

 

Test result

Below is my received sample email for workflow approval.

After click approve/reject hyperlinks, the web page will be redirected to below new page where you can add some comments for approval/rejection–

The process can even be done on your smart phone –

The workflow is processed and you can check the comments from AX client > workflow history –

Side notes for troubleshooting

When you test the approval via email by clicking the link in email, you might get below error information and cannot proceed with approve/reject.

Checking the connector UI, you’ll notice only one Config service is showing (generally you should see 2 services showing in Started section – …/config, and …/email)

Resolution –

This issue is caused by wrong value (or even empty value) for EmailApprovalService on mobile connector UI. You need to fix the connector parameter by providing correct value for parameter EmailApprovalService (this is from the step #3 – create inbound ports, you need to create it manually in AX > inbound ports form. More guidance can refer to the whitepaper for workflow approval via email), you’ll get 2 services showing in the connector UI (Email & Config) which is expected. And above issue you see from web browser will be gone.

 

↧
↧

Using Power Platform Dataflows to extract and process data from Business Central – The Movie

September 22, 2019, 11:56 pm
↧

Boost your ecommerce revenue with Dynamics 365 Fraud Protection

September 23, 2019, 8:00 am
$
0
0

With the booming growth of online technologies and marketplaces comes the burgeoning rise of a variety of cybersecurity challenges for businesses that conduct any aspect of their operations through online software and the Internet. Fraud is one of the most pervasive trends of the modern online marketplace, and continues to be a consistent, invasive issue for all businesses.

As the rate of payment fraud continues to rise, especially in retail ecommerce where the liability lies with the merchant, so does the amount companies spend each year to combat and secure themselves against it. Fraud and wrongful rejections already significantly impact merchants bottom-line in a booming economy and as well as when the economy is soft.

The impact of outdated fraud detection tools and false alarms

Customers, merchants, and banking institutions have been impacted for years by suboptimal experiences, increased operational expenses, wrongful rejections, and reduced revenue. To combat these negative business impacts, companies have been implementing layered solutions. For example, merchant risk managers are bogged down with manual reviews and analysis of their own local 30/60/90-day historical data. These narrow, outdated views of data provide a partial hindsight view of fraud trends, leaving risk managers with no real-time information to work with when creating new rules to hopefully minimize fraud loss.

One of the most common ways that fraud impacts everyday consumers and business is through wrongful rejections. For example, when a merchant maintains an outdated and/or strict set of transaction rules and algorithms, a customer who initiates a retail ecommerce transaction through a credit card might experience a wrongful rejection known to consumers as a declined transaction, because of these outdated rules. Similarly, wrongful declined transactions can also happen when the card issuing bank refuses to authorize the purchase using the card due to suspicion of fraud. The implications of these suboptimal experiences for all parties involved (customers, merchants, and banks) directly correlates into loss of credibility, security, and business revenue.

Introducing Microsoft Dynamics 365 Fraud Protection

As one of the biggest technology organizations in the world, Microsoft saw an opportunity to provide software as a service that effectively and visibly helps reduce the rate and pervasiveness of fraud while simultaneously helping to reduce wrongful declined transactions and improving customer experience. Microsoft Dynamics 365 Fraud Protection is a cloud-based solution merchants can use in real-time to help lower their costs related to combatting fraud, help increase their revenue by improving acceptance of legitimate transactions, reduce friction in customer experience, and integrate easily into their existing order management system and payment stack. This solution offers a global level of fraud insights using data sets from participating merchants that are processed with real-time machine learning to detect and mitigate evolving fraud schemes in a timely manner.

Microsoft Dynamics 365 Fraud Protection houses five powerful capabilities designed to capitalize on the power of machine learning to provide merchants with an innovative fraud protection solution:

  • Adaptive AI technology continuously learns and adapts from patterns and trends and will equip fraud managers with the tools and data they need to make informed decisions on how to optimize their fraud controls.
  • A fraud protection network maintains up-to-date connected data that provides a global view of fraud activity and maintains the security of merchants confidential information and shoppers’ privacy.
  • Transaction acceptance booster shares transactional trust knowledge with issuing banks to help boost authorization rates.
  • Customer escalation support provides detailed risk insights about each transaction to help improve merchants customer support experience.
  • Account creation protection monitors account creation, helps minimize abuse and automated attacks on customer accounts, and helps to avoid incurring losses due to fraudulent accounts

See the image below to learn more about the relationship between merchants and banks when they both use Dynamics 365 Fraud Protection:

Dynamics 365 Fraud Protection increases bank acceptance rates and decreases false positives by sharing transaction risk exposure with issuers so they can make more informed assessments.

Banks worldwide can choose to participate in the Dynamics 365 Fraud Protection transaction acceptance booster feature to increase acceptance rates of legitimate authorization requests from online merchants using Dynamics 365 Fraud Protection. Merchants using the product can opt to use this feature to increase acceptance rates for authorization requests made to banks without having to make any changes to their existing authorization process.

Learn more

This week at Sibos 2019 in London, Microsoft will be showcasing its secure and compliant cloud solutions for the banking industry. Read a round-up of announcements unveiled at Sibos and view an agenda of Microsoft events and sessions at the show. Stop by our booth (Z131) for a showcase of applications relevant to banking, including Microsoft Dynamics 365 Fraud Protection, which will be generally available on October 1st, 2019. Contact your Microsoft representative to get started.

The post Boost your ecommerce revenue with Dynamics 365 Fraud Protection appeared first on Dynamics 365 Blog.

↧

Block time off for resources on the schedule board without changing the working hours

September 23, 2019, 8:59 am
$
0
0

I was recently chatting with a dispatcher who expressed that they would like to block time off on the schedule board for resources without needing to interact with the working hours.

I am switching gears on this post putting on my implementor hat. We will look for ways to enable this scenario natively in the product but until then, your customers may have this need. Here is a creative way you may be able to accomplish the request. It isn’t perfect, but an idea nonetheless!

The goal is for a dispatcher to stay completely within the schedule board yet block time off for a resource.

At a high level, we will create a new entity and enable it for scheduling. This entity is strictly for tracking “blocked time”. Then, we will create bookings for this entity from the schedule board to block the time. We will ensure these bookings look visually different on the schedule board.

The Setup:

Enabling the "block time" entity for scheduling

 

  • Create a record in the block time table.
Creating a "block time" record called "block time on the board"
  • Create a resource requirement for that block time record. There is no need to enter a duration; you just need the name.
Create a new resource requirement record
  • Create a resource requirement view that shows all requirements if the booking setup metadata = Block Time
    • You only need one resource requirement for the entire organization, but you could opt to create different ones for different territories or dispatchers. That is up to you! In this case, I am assuming there is only one record that the entire organization shares.
Creating a view on the resource requirement entity where booking setup metadata = "block time"
  • Optionaladd a new booking requirements tab (requirements panel) to the schedule board dedicated to showing this “block time” requirement.
    • Pro Tip! You can add this to the default schedule board, and then all schedule boards will see this tab unless a board is set to hide default requirement panels.

 

The Action:

Dispatchers can now block off time in two ways:

Option 1: Just drag empty space on the board where you want to block off time. This will pop out the requirements panel. Find the requirement we created earlier and select it. If it is not included in the view, you may have to change views to see that requirement.

Drag empty space on the schedule boardSelect requirement in the flyout panel created earlierBooking showing on the board created for blocking time

Option 2: The second option applies if you implemented the optional step above where we added a booking requirements tab/panel with the “block time” requirement. You can just drag the block time requirement to the resource and time you would like to block off. Since there is no duration on the requirement, it will default to the duration set on the BSM record. You can always drag to extend or reduce the duration.

Here you can see me dragging the “block time” requirement from the “block time” requirement panel to Joseph at 3 PM.

Dragging from bottom panel to board

Here you can see the booking blocking the time that Joseph created:

Booking created after dragging to the board

Notice the requirement is not removed from the bottom panel. This is because the filter we created does not exclude bookings which have already been scheduled. This allows you to drag this requirement repeatedly to create “block time” bookings.

You can also accomplish this from the multi-day schedule boards by selecting the day, week, or month you would like to block off. Make sure you select the requirement, and how much time you want to block. If you want to block the entire selected duration, just choose full capacity.

On the daily schedule board, selecting the "block time" requirement, the day I want to block, and changing the booking method to full capacity and booking itSchedule board showing 8 hours booked with the underlying booking on the daily board

Additional Tips:

  • You can use a different booking status for time off. Just create a new booking status and set this status to be the default status on the block time booking setup metadata record. You can change the color of the status, so it looks different on the board. You can also make sure this status cannot be used for bookings related to any other entities. To learn more about booking statuses, check out the documentation and my previous blog post for even more advanced functionality.

Here I am creating a new booking status and setting the color to gray:

a screenshot of a cell phone

Here I am setting the default committed status on the “block time” booking setup metadata record to the status I just created:

Changing the default booking status on the booking setup metadata record to the "block time status"

Here you can see the booking appearing in gray on the board:

"Block time" booking with the color gray
  • You can also change the template for the block time bookings to show whatever info you would like. Just modify the booking template on an individual board, or at a global level for all users. Remember, you can have a different template for each schedulable entity, meaning you can have different information appear on “block time” bookings than work order bookings.
  • If you are using RSO, make sure you set the booking status you plan to use to do not move so resource scheduling optimization knows not to move these bookings.
  • If you use the apply filter territory setting on the board, which filters the requirements panel based on the territory searched in the filter panel, you will need a different requirement per territory to use the tabs on the bottom.
Apply filter terrirory setting under the setting icon on the schedule board

Cautions:

  1. By using bookings, make sure your reports exclude these block time bookings.
  2. The resource template percentage and hours booked calculations will treat these hours as if they are booked. This may be an issue or may not matter depending on your implementation and usage of those numbers.
Schedule board showing the resource cell percentage and booked duration reflecting the "block time" bookings. Also shows the multi-day view showing those hours as booked

Happy scheduling!

Dan Gittler, Principal PM

The post Block time off for resources on the schedule board without changing the working hours appeared first on Dynamics 365 Blog.

↧
Search

The DynamicsFinancials connector will be turned off September 30, 2019

September 24, 2019, 6:00 am
$
0
0

Last year, we published a notification regarding the deprecation of the Project Madeira and Dynamics 365 for Finance and Operations, Business edition connectors for Power BI, Microsoft Flow and PowerApps, the DynamicsFinancials connector. The deprecation was to happen on December 31, 2018. Due to a larger number of customers still using the old connector, we continued to make it available in our service to give users more time to make their updates. This time is now up.

On September 30, 2019 the DynamicsFinancials connector will be turned off in our service. Any existing PowerApp, Logic App, or Flow using this old connector will no longer work.

An update to the Dynamics 365 Business Central connector used for Microsoft Flow, Logic Apps, and PowerApps was released the week of September 16, 2019, and we recommend that you use this as a replacement.

Call to action

Update any existing Microsoft Flows, Logic Apps, or PowerApps that were created using the DynamicsFinancials connector.

Instructions on how to update to the latest connector can be found in this blog post.

 

The post The DynamicsFinancials connector will be turned off September 30, 2019 appeared first on Dynamics 365 Blog.

↧
↧

Announcing Customer Service Insights availability in France geographic area

September 24, 2019, 12:24 pm
$
0
0

We are very excited to announce that Dynamics 365 Customer Service Insights is now available in France-based datacenters! This is in addition to the nine other geographic areas weve supported since general availability.

When Customer Service Insights creates workspaces, it generates and stores the insights data in the same geographic area as where your case data is stored in the Common Data Service (CDS) database. Given the CDS has recently expanded the geographic area to France, this support ensures all insights data generated from your cases stored in France will stay in France. It can also improve the performance of your workspace refresh.

Below is a full list of data locations that Customer Service Insights supports today. More details can be found in the article Where an organization’s Customer Service Insights data is located. You can also learn more from this article about Microsoft Cloud France.

Azure geographic areas (geos)Azure datacenters (regions)
EuropeWest Europe (Netherlands)
North Europe (Ireland)
United StatesEast US (Blue Ridge, VA)
South Central US (Des Moines, IA)
West US (Quincy, WA)
AustraliaAustralia East (New South Wales)
Australia Southeast (Victoria)
Asia PacificSoutheast Asia (Singapore)
East Asia (Hong Kong)
United KingdomUK South (London)
UK West (Cardiff, Durham)
BrazilBrazil South (So Paulo State)
CanadaCanada Central (Toronto)
Canada East (Qubec City)
IndiaCentral India (Pune)
South India (Chennai)
JapanJapan East (Tokyo, Saitama)
Japan West (Osaka)
FranceFrance Central (Paris)
France South (Marseille)

 

As always, your feedback is critical for us to prioritize whats next. If you have any suggestions or ideas, please dont hesitate to submit an idea or vote on others ideas.

If you have questions about this support or any other features, were always available at the Customer Service Insights forum to help you.

 

Enjoy!

 

To learn more, visit:

The post Announcing Customer Service Insights availability in France geographic area appeared first on Dynamics 365 Blog.

↧

New process to submit support requests for Dynamics 365 Business Central

September 25, 2019, 7:00 am
$
0
0

The Business Central Administration Center has been updated so that partners can submit requests for support. Use the question mark in the top right corner, and then, from the menu, choose the New Support Request menu item.

a screenshot of a cell phone

 

 

This link directs you to the Power Platform Admin Center where you submit the actual support request.

Once you’re on the support request page, the customer that you are submitting on behalf of shows in the information pane automatically. Next, specify the product as Dynamics 365 Business Central, then the problem type and category.

A new feature with this portal is suggested solutions. Just type something in the Tell us what you need help with area, then choose See solutions. Choose any of the suggested solutions to see the detailed documentation. If these do not resolve the issue, then click Create a support request at the bottom of the pane.

On the next screen you must enter your support Access ID and Contract ID/password. For help with this information, contact your account manager. This is a one-off for your organization, and if you have to submit a support request later, the information is saved so that you can just choose it in the request pane.

Next, enter the issue title and a description, and optionally upload attachments. Choose Next. Finally, enter your contact information and submit the ticket.

Additionally, you can start from the Microsoft Partner Center to direct you to the Power Platform Admin Center. For more information, see View solutions or enter a support request through the new support center in the PowerApps administration content.

The post New process to submit support requests for Dynamics 365 Business Central appeared first on Dynamics 365 Blog.

↧

Release Notes for Project Service Automation Update Release 19, V2.4.16.40

September 27, 2019, 7:20 am
$
0
0

Were pleased to announce the latest update for the Project Service Automation application for Dynamics 365. This release includes bug fixes.

This release is compatible with Dynamics 365 9.x. To update to this release, visit the Admin Center for Dynamics 365 online, solutions page to install the update. For details, refer How to Install, Update a Preferred Solution

 

Project Service Automation (V 2.4.16.40)

  • Bug Fixes
  • Fixed: Out of the Box webclient SalesOrder form ribbon is flashing when msdyn_OrderType is null.
  • Fixed: Adding Ampersand (‘&’) In Time Entry Rejection Comments throws error.

 

Were pleased to announce the latest update for the Project Service Automation, V2.4.15.33, application for Dynamics 365. This release includes bug fixes.

This release is compatible with Dynamics 365 9.x. To update to this release, visit the Admin Center for Dynamics 365 online, solutions page to install the update. For details, refer How to Install, Update a Preferred Solution

Bug Fixes

  • Fixed: Entity Views not following ‘Only Related Records’ data source rules.

End of Life Notice

Note: After February 2020, we will no longer support Field Service and Project Service Automation legacy versions.

This includes:

  • Project Service Automation (PSA) version 1.x or 2.x
  • Field Service (FS) version 6.x or 7.x

Please ensure that you have plans to upgrade to the latest version of these solutions. These solutions should be upgraded no later than February 2020.

Administrators can follow instructions to enable their environments to install the latest PSA or FS, or you can contact support to enable the install on your organizations.

We have published a quick start guide with special focus on Field and Project Service to help organizations get started in the upgrade process.

Lastly, please plan to conduct the upgrade and test your use cases in a non-production environment prior to conducting this upgrade on a production environment.

 

 

Project Service Automation Team

The post Release Notes for Project Service Automation Update Release 19, V2.4.16.40 appeared first on Dynamics 365 Blog.

↧

Learning paths for Dynamics 365 Business Central on Microsoft Learn

September 30, 2019, 1:00 am
$
0
0

We’re proud to announce that you can now find learning paths and e-learning modules on Microsoft Learn specifically for Dynamics 365 Business Central.

MS Learn filtered for Dynamics 365 Business Central

You can use this new content to educate yourself about business functionality, or to brush up on how to use multiple currencies, for example. Microsoft Learn is a completely free, open training platform available to anyone who has an interest to learn about Microsoft products – check out the FAQ!

To help you get started, we provide learning paths for the complex and not-so-complex end-to-end processes:

MS Learn filtered for learning paths for Business Central

This e-learning library has been developed in a partnership between the Business Central team and e-learning specialists from Microsoft and the partner community. New content will be added in the coming weeks, so go to https://aka.ms/learn, set a filter for Business Central, and start learning!

 

Best regards,

Margo Crandall, Business Applications Group Learn

Eva Dupont, Business Applications Content Experience

 

The post Learning paths for Dynamics 365 Business Central on Microsoft Learn appeared first on Dynamics 365 Blog.

↧
↧

Tivoli Gardens personalizes the guest experience with Customer Insights

September 30, 2019, 9:00 am
$
0
0

Meet Bernt Bisgaard Caspersen, Head of architecture and IT delivery at Tivoli Gardens in Copenhagen; one of the worlds longest running amusement parks. Since opening in 1843, Tivoli was modeled after the now defunct Parisian Tivoli and Vauxhall Gardens in London, and offers guests thrill rides, live entertainment, arcade games, dining, hotels, and a garden with 115,000 flowers.

Bernt and his small team are responsible for maintaining the IT infrastructure and technology systems for the park properties, including multiple, complex customer and business databases. This is a tall order that Bernt and his team strive to achieve daily. Being a small team, it can be a challenge to pick the right tools to be efficient and deliver every time.

To provide an exceptional visit for todays digitally-connected guest, Tivoli has set out to ensure a consistent, personalized experience across every touchpointfrom the first visit to the Tivoli website, to the hotel reservation to onsite experiences.

Tivoli generates a massive amount of guest data from annual cardholders, ticket systems, and digital and human touchpoints. For instance, Tivoli tracks which rides the guests took, which concert was attended on which day and more. Tivoli uses this information to further improve the Tivoli experience, making it even more personal with each visit. The goal is to have the conductor at the ticket office make suggestions to a guest based on the music, rides, food, and other experiences theyve previously enjoyed.

The problem with generating a lot of data is that you must have a way of analyzing it and uncovering actionable insights. Bernt understood the dilemma and sought ways to make the data come alive so it could be useful. Bernt wanted to dig into the data, down to each individual guest so every Tivoli employee could provide a better guest experience.

Bernt began looking into Microsoft Dynamics 365, as Tivoli was currently using Dynamics applications and was pleased with the products. Bernt researched Dynamics 365 Customer Insights, an AI-enabled application that unifies data across sources and presents a single view of customers. Bernt was quickly convinced that this would solve his live data issue.

Bernt believed that conductors could leverage Customer Insights single guest view to personalize every guest experience, increase engagement, and strengthen loyalty. He surmised that such an application could help predict the likelihood of guests returning and be key to gaining insights into creating exceptional experiences. He also believed Customer Insights and the Dynamics 365 platform would continue to help Tivoli in even more ways in the future.

Since integrating Customer Insights, Tivoli has been able to further strengthen their bond with guests by enhancing their guest services. They are also beginning to leverage data from digital channels including newsletters, e-surveys, online offers, website visits, and e-commerce, to garner even more actionable insights. These insights empower employees to further personalize the guest experience and aid in more precise guest marketing with personalized emails, invitations, and alerts to upcoming events.

Tivoli is building on the captured data by calculating insurance goals, probability of returning guests, and segmenting guests according to loyalty and lifetime spend. Guests are rewarded in the loyalty program with targeted incentives such as a backstage pass or inner circle entrance. The goal is to spread investments in loyalty, and prevent churn and to do that, Tivoli depends on Dynamics 365 Customer Insights. Customer Insights continues to exceed expectations, contributing to Tivoli ranking in the top ten of the net promoter score.

Bernt is a Dynamics 365 hero. He had a vision and is continuing to shape that vision through Dynamics 365 Customer Insights. He is the catalyst of change at Tivoli, helping to reinvent itself by leveraging data and artificial intelligence to drill down into the preferences of every guest and further personalize the guest experience. Bernt has helped create a wonderous experience for every Tivoli guest and its paying off.

Read more about Tivoli Gardens and Customer Insights

Take a closer look at how Tivoli Gardens is personalizing guest experiences with Dynamics 365 Customer Insights.

The post Tivoli Gardens personalizes the guest experience with Customer Insights appeared first on Dynamics 365 Blog.

↧

Release Notes for Field Service Mobile app version 11.3 and mobile project template version 1.0.2735

September 30, 2019, 3:36 pm
$
0
0

Field Service Mobile: Version 11.3

A new version of Field Service Mobile for Windows, iOS, and Android has been released! Here are fixes and updates you can expect:

– Fixed update address button error message

– Fixed unresponsive iOS buttons

– Disabled password clearing for OAuth

– Fixed SQLite error during loading configuration

– Add logging of sync filters

– Minimum Android version is now 5.0

– Fixed date picker on Android

– PushRegistrationIntentService start fixed for Android 8+

– Android reminders fixed

– Added missing barcode scanning permission

– Ability to clear logs

– Double message popup prevention added

– Bluetooth scanner functionality

– Auto-setting of CRM timezone

– Added handler for JSBridge method isInternetConnected

– Ability to call ExecuteWorkflowAction JSBridge method with an EntityReference parameter

– Enforced minimum for GPS Age and Accuracy

– Changed deep link schema to fsmobile

– Fixed issue on iOS where user was not prompted to grant “Always” location permission to app

– Changed Location Tracking Title and added a message body for Android location tracking notifications

– Fixed saving of offline Booking Signatures

– Compatible with Azure Blob Storage for note attachments

– Field Level Permissions defined in Dynamics 365 now respected

 

Mobile Project Template Version 1.0.2735

A new mobile project template has also been released. A mobile project contains all customizations of the Field Service Mobile app. This is where you can add/remove/change fields, entities, views, forms etc. Note: If you are using the previous mobile project template (version 1.0.1322) you should import the new project as a derivate of the previous. See instructions here.

Download the latest mobile project at https://aka.ms/fsmobile-project.

– Removed “Failed” error that happens when backing out of Scan Customer Asset

– Added filters so that app does not sync inactive records

– Ignore ‘seconds’ part when calculating current time in TravelingCalculations.js

– Added sync filter for booking timestamps

– Added ability for CFS to embed PowerBI to forms

Keep track of Field Service version history.

 

The post Release Notes for Field Service Mobile app version 11.3 and mobile project template version 1.0.2735 appeared first on Dynamics 365 Blog.

↧
Search

Announcing general availability of Dynamics 365 Guides!

October 1, 2019, 9:12 am
$
0
0

We’re thrilled to announce the general availability of Dynamics 365 Guides today!

Dynamics 365 Guides app version 200.1909.24001 and solution version 200.0.0.102 include the following updates:

  • Try the demo. You can now try an out-of-the-box sample guide on the HoloLens app without signing up for a license or authoring a guide yourself.
  • Customer satisfaction surveys. We will occasionally ask you to rate your satisfaction with Dynamics 365 Guides to help us improve the product.
  • Opt out of sending data to Microsoft. On both PC and HoloLens apps, for privacy reasons, you can turn off the ability to send telemetry data to Microsoft.
  • Opt out of sending usage data to your organization. To prevent usage data from appearing in Power BI dashboards, administrators can now turn this off for specific users.

Current customers must update the PC app, HoloLens app, and Common Data Service solution to continue using Dynamics 365 Guides. See update instructions.

Note that this update will continue to work with your preview license until it expires. To check your preview license expiration date, go to https://admin.microsoft.com/, and then select Billing in settings.

For new customers, we recommend acquiring a new GA license and installing the apps by following the instructions at aka.ms/GetGuides.

 

The post Announcing general availability of Dynamics 365 Guides! appeared first on Dynamics 365 Blog.

↧

Dynamics 365 Remote Assist goes GA in the October 2019 update!

October 1, 2019, 9:12 am
$
0
0

Applies to: Dynamics 365 Remote Assist (version 2019.10.01)

Microsoft Dynamics 365 Remote Assist for mobile is now generally available!

Users already familiar with Dynamics 365 Remote Assist on HoloLens can access many of the same collaboration tools with just their cell phone or tablet. The Dynamics 365 Remote Assist user on an Android or iOS phone or tablet can place a one-to-one call with an expert using Microsoft Teams to solve complex problems together. Both devices on the call can create mixed reality annotations, such as inking and placing arrows, that appear in the real world.

Dynamics 365 Remote Assist for mobile screens

Additionally, as of the October 2019 update:

  • Both users can also annotate on a high-quality image capture from the phone for more precise detail and to conserve battery life.
  • Users can take advantage of text chat.
  • Users can get a quick overview of the app by accessing a new tutorial.

For more information on setting up and using Dynamics 365 Remote Assist for mobile, see the Dynamics 365 Remote Assist for mobile user guide.

 

 

The post Dynamics 365 Remote Assist goes GA in the October 2019 update! appeared first on Dynamics 365 Blog.

↧
↧

Release wave 2 launches with over 400 updates, new apps, and industry solutions

October 1, 2019, 9:30 am
$
0
0

2019 release wave 2 launches with new applications and hundreds of capabilities across Dynamics 365 and the Power Platform.

Today marks the general availability of more than 400 new feature updates and capabilities across Dynamics 365 and the Power Platform. This release waveone of our largest to dateshowcases our continued investment in artificial intelligence to unlock proactive insights and drive intelligent action to accelerate your business transformation.

The updates Ive highlighted belowin addition to new AI-infused and industry-focused capabilities announced last weekare reflected in the latest release notes for Dynamics 365 and the Microsoft Power Platform. Well also highlight some of these capabilities at our Virtual Launch Event on Thursday, October 10th.

AI goes to work for proactive, predictive business results

As market disrupters know, a business can no longer function in a vacuum with teams, ideas, and data locked in silos. Thats why Microsoft has invested billions of dollars in AI research to bring insights to everyone in context of the task at handa key to transforming from a reactive to proactive organization.

With this release, were introducing a wave of new AI-infused applications and capabilities that enable more people across the organization to take informed actions and deliver exceptional personalized experiences, powered by an unprecedented level of advanced intelligence being delivered with Microsoft Dynamics 365 applications.

As announced last week, Dynamics 365 Product Insights will connect product telemetry to Microsoft Business Applications, bringing insights from connected physical products and give visibility into product performance and customer interactions. For organizations like Ecolaban innovator in water, hygiene and energy technologiesDynamics 365 Product Insights will capture real-time information from products like dishwashers, providing deeper insights that can reduce water usage while increasing product performance and reliability.

In addition, were enhancing applications to help organizations better understand and serve customers. An update for Dynamics 365 Customer Insights will go beyond B2C scenarios to allow your organization to generate insights into complex B2B journeys to better understand and serve leads and accounts. Read how segment leaders Marstons and Tivoli are finding success with Customer Insights.

Dynamics 365 Virtual Agent for Customer Service, currently in preview, will be enhanced with new authoring capabilities to more rapidly test and deploy AI-powered chat bots to free agents to focus on more complex issues, while providing deep insights into customer satisfaction metrics. For instance, TruGreen, the largest lawn care company in the U.S., is deploying a Dynamics 365 Virtual Agent to respond faster to its 2.3 million customers.

Browse the release notes for a comprehensive overview of new and improved features to our growing portfolio of insights applications powered by Azure AI.

Reimaging retail

The future of retail is all about connected experiencespersonalized, secure, and friction-free experiences shoppers expect.

To deliver this unified experience, retailers need intelligent business practices driven by connected data to optimize operations, inventory, supply chain, fulfillment, service, and frontline, customer-facing interactions. Dynamics 365 Commerce delivers on these needs. Its an omnichannel solution for retail and e-commerce companies that unifies back office, in-store, call center and digital experiences, providing frictionless, consistent engagement across every online and offline channel. Ste. Michelle Wine Estates, the third largest premium wine company in the U.S., is one of the first organizations to deploy Dynamics 365 Commerce.

Just as important, retailers need insights from data beyond transactions and clicks, such as observational data generated as customers move through physical retail spacesuntapped data sources that can help retailers make sense of their entire business, enabling them to act faster and run smoother. Dynamics 365 Connected Store delivers a new level of insight into the retail space by analyzing data from video cameras and IoT sensors to provide real-time and predictive insights to optimize the in-store experience. Connected Store unlocks the ability for retailers to be proactive in every aspect of their business, from alerting staff to restock shelves, optimizing store layouts to tracking long-term trends in shopping patterns week-by-week, season-to-season.

Together, these applications bridge data-driven intelligence with modern business applications that help retailers deliver the personalized, differentiated shopping experiences consumers expect.

More secure and personalized banking and commerce

Last week at Sibos 2019, the annual banking and financial conference hosted in London, weannounced a trifecta of enhancements to empower intelligent banking with AI on our secure, compliant cloud.

Dynamics 365 Fraud Protection is generally available starting today, providing a powerful fraud protection solution to decrease fraud costs and help increase acceptance rates for customer payment transactions with e-commerce merchants. Learn how Microsoft reduced fraud-related costs by $76 million over a two-year period using the technology now available to every organization.

We also enhanced the Microsoft Banking Accelerator, released in July, with use cases for retail banking and sample APIs for interoperability with the Banking Industry Architecture Network (BAIN). These enhancements enable banking and financial organizations to rapidly build intelligent, data-driven solutions across retail and commercial lines of business, accelerating time to value for a range of customer scenarios.

Power Platform: new capabilities to analyze, act, and automate

Ive said it before, and Ill say it again: the Microsoft Power Platform community is second to none, inspiring us to deliver in each release the improvements and new capabilities to help you and your organization achieve more. Were excited to share this wave of updates across PowerApps, Microsoft Flow, and Power BI.

Were updating PowerApps with improvements to help you build higher-quality apps more easily and better engage your customer and partners. Portals, allows anyone to build a low-code web portal that surfaces data stored in Common Data Service to employees or users outside their organizations. Check out the full list of PowerApps updates.

Microsoft Flow makers will find new features for smarter and more powerful experiences that let them leverage world-class business process capabilities, including working with business processes offline. And administrators benefit from richer tooling, such as PowerShell Command lets (cmdlets) and the new Power Platform Admin Center. See whats new with Flow.

AI Builder is now generally available in PowerApps and Microsoft Flow, allowing everyone from pro developers to front-line workers to build apps and workflows that leverage AI models based on our low code platform.

For this release, weve focused Power BI updates on four key areas that drive a data culture: intuitive experiences, a unified BI platform, big data analytics, and pervasive artificial intelligence (AI). Check out the full list of Power BI updates.

Attend our Virtual Launch Event for a closer look at this waves highlights

We invite you to attend our Virtual Launch Event on Thursday, October 10th streaming live at 8:00 am Pacific time, then on-demand, for a first look at the new innovations coming to market. Be sure to register for updates and reminders leading up to the event, and check out our October release page for detailed release plans for Dynamics 365 and the Power Platform, key dates and deep dive demo videos.

The post Release wave 2 launches with over 400 updates, new apps, and industry solutions appeared first on Dynamics 365 Blog.

↧

Lifecycle Services – October 2019 (Release 1) release notes

October 1, 2019, 9:33 am
$
0
0

Database movement API in private preview We are excited to announce that the database movement RESTful API is now in private preview. This release includes authenticating with the service, listing the available databases in the asset library, creating a database refresh between two environments, and polling for ongoing status. To help provide feedback and learn

Read more

The post Lifecycle Services – October 2019 (Release 1) release notes appeared first on Dynamics 365 Blog.

↧

Announcing Microsoft Dynamics 365 Product Insights – Now in preview

October 2, 2019, 9:00 am
$
0
0
Im thrilled to introduce a new analytics application in the Microsoft Dynamics 365 portfolio which gives organizations real-time visibility into how customers use their products or services. Called Microsoft Dynamics 365 Product Insights, the application is for enterprises that design, build, manage, or service connected products and services with intermediated software. Dynamics 365 Product Insights helps you take actions in the moment to move from simply conducting transactions to delivering rich, ongoing customer relationships. You can sign up for the preview today.

Rising customer expectations creates the need to know your customers more deeply than ever before, and to respond to their needs more fully.

Innovations in customer service have introduced an entirely new dimension of connected experiences. Organizations are striving to make that experience as consistent as possible. Customers today want companies they do business with to get them and provide personalized service, whether theyre in a B2B or B2C world. They want fast responsiveness to any request, and for their orders to be shipped promptly. If they opt for self-service support, they want it to feel high-touch, almost human.
At Microsoft, we want to empower you to meet all these expectations, and more. Thats why were introducing Dynamics 365 Product Insights. To empower every organization to build the most comprehensive view of their customers and how customers are using their products.

Digitally transform the entire customer journey through the use of product telemetry.

Dynamics 365 Product Insights provides you with real-time visibility into your connected physical product and digital experiences by collecting signals and acquiring a live stream of data for real-time analysis. As a result, you can monitor and learn from customer interactions in the moment, and proactively deliver more personalized and responsive end-to-end customer experiences. With capabilities designed for business users, anyone in your organization can make data-informed decisions, without requiring specialized data science knowledge or coding skills. You can pursue new upsell, partnership, and subscription opportunities that drive revenue by adding connected data to products and services.

Microsoft Dynamics 365 Product Insights brings value to Microsoft Dynamics 365 Customer Insights to provide a more complete understanding of the customer.

At Microsoft, were always looking for ways to maximize the lifetime value of your customers. Earlier this year we introduced Dynamics 365 Customer Insights, which unifies your disparate data to provide a single, 360-degree view of customer data. Dynamics 365 Customer Insights reveals who your customers are and what they want. Dynamics 365 Product Insights shows how they use your products. When used together, they help you deliver a much more engaging experience as well as discover new ways to provide value.

Dynamics 365 Product Insights leverages the AI and machine-learning components of Azure AI with the customer data platform (CDP) elements of Dynamics 365 Customer Insights to help you better engage with your customers and transform your product development, sales, and support.

Learn more about Dynamics 365 Product Insights and try it for yourself by using our preview.
Screenshot of public preview view

Virtual Launch Event for a closer look at Dynamics 365 Product Insights

We invite you to attend our Virtual Launch Event on Thursday, October 10th streaming live at 8:00 am Pacific time, then on-demand, for a look at Dynamics 365 Product Insights and all the other new innovations coming to market. Be sure to register for updates and reminders leading up to the event.

The post Announcing Microsoft Dynamics 365 Product Insights – Now in preview appeared first on Dynamics 365 Blog.

↧
Viewing all 678 articles
Browse latest View live
Search