By default, Microsoft Dynamics 365 Government sets a user session timeout of 8 hours. A user is not required to log in with their credentials for up to 8 hours regardless of whether the user was active or inactive.
With the implementation of the Security enhancements: User session and access management, you can now set your own session timeout limit for your individual Dynamics 365 instances.
For greater flexibility and better customer experience, we are moving the maximum session timeout duration from 8 hours to 24 hours. This would allow you to set a custom session timeout duration between 1 hour and 24 hours.
If you need to maintain the 8-hour session timeout duration, you will need to set a custom session timeout for all your Dynamics 365 instances.
Please refer to FedRAMP guidance on recommended activity and session timeout parameters for your organization.
Please see highlights of these enhancements in the following video: Security Enhancements: User session management.
Microsoft Social Engagement 2017 Update 1.10 is ready and will be released in November 2017. This article describes the fixes, and other changes that are included in this update.
Microsoft Social Engagement 2017 Update 1.10 introduces the following features:
To make activity maps more accessible to everyone, we introduced shapes as an additional means of displaying information on the maps. Sentiment values and the age of posts are now expressed in color and shape.
Alert emails now provide a link to the Analytics area in the Social Engagement app, where you can see the posts that match the data set that triggered the alert. Post content is no longer delivered as part of the email message. These links now also reflect changed alert configurations and deleted alerts.
Learn how to build search topics and navigate Social Engagement to get the most out of it. Plus, examine different strategies for managing your social presence. Explore the social engagement circle and social strategy, and look at brand reputation and social business opportunities. Take a look at post consumption and analytics, configure automation options, and much more.
Learn more in the Microsoft Social Engagement course on MVA.
Next to the 10,000 monthly post package for Microsoft Social Engagement, new packages with 100,000 and 1,000,000 monthly posts are now available as part of the Microsoft Products and Services Agreement (MPSA). The MPSA is a transactional licensing agreement for commercial, government, and academic organizations that have 250 or more users or devices.
In addition to the new features, Update 1.10 addresses the following issues:
With the release of Dynamics 365 (online), version 9.0, there are a lot of changes in our developer documentation:
A Software Development Kit (SDK) is a combination of documentation and resources that developers use to build software. Until now, we were using the term “SDK” to refer to the developer documentation for Dynamics 365 Customer Engagement and for the download package containing assemblies, tools, and the offline (CHM) version of the documentation. To clear up this confusion, and to be consistent with the terms we use for all our documentation, we will now refer to the developer documentation as the Developer Guide. This is a more descriptive name for the content that supports developers in creating software using the available APIs.
Probably the greatest single change is that we are no longer providing a single download package for all the documentation, tools and sample code.
Going forward, instead of shipping a single package with everything in it, we will offer an a-la-carte approach so that you can download the individual things as you need them.
In the documentation for previous versions the conceptual content came first, followed by the programming reference topics (Dynamics 365 Customer Engagement Programming reference). While the conceptual pages linked to the relevant reference pages, this caused you to lose context of the page you were reading.
One of the cool features of docs.microsoft.com is the ability to present reference and conceptual content together. This provides the opportunity to bind the relevant conceptual content together with the most relevant reference content. This allows for fusion of the conceptual and reference information for a specific set of APIs.
Here are the individual links to programming reference:
The client scripting or client API has grown a lot since it was originally introduced with CRM 2011. With this release, we have restructured the content to allow for better search results for individual APIs by providing dedicated pages for each API. This should help improve discoverability and provide us with more space to grow with samples and any new APIs which may come.
We have added new information to help you get started: Walkthrough: Write your first client script.
For a long time, we have written individual topics about selected entities where we provide a broad overview of the entity and relationships along with some lists of supported messages. But when it came to details, we referred you to use separate tools to browse the metadata for your organization or to refer to an Excel spreadsheet in the SDK package.
For this release, we are leveraging the entity metadata to generate reference documentation for most entities in the system together with a complete list of all the properties, attributes and relationships. You can find this here: Entity Reference. This is similar to the Web API EntityType Reference, which still exists, but the new entity reference also reflects the structures used when programming with the SDK assemblies.
Included with the entity reference is a listing all the available operations for each entity. There are links describing which operations can be performed using either the Web API or the SDK assemblies. You can see an example of this here for the Account entity messages.
Entities for common solutions
This entity reference can’t contain any custom entities you have in your system. But it does include entities, attributes, and relationships added by the following common add-on solutions available for Dynamics 365:
These solutions have entities with names that begin with msdyn_. For example the msdyn_approval Entity is added by the Project Service Automation Solution.
We hope that you find these changes valuable, and we would love to hear your feedback. If you find something wrong or have ideas for improvements to the Developer Guide, please let us know by using the comment capability at the bottom of each page. To provide feedback on Dynamics 365 features, please add or vote up your ideas here: https://ideas.dynamics.com/ideas/.
Applies to: Dynamics 365 v8.2 organization with Project Service Automation(v18.104.22.168), Dynamics 365 v8.2 organization with Field Solution(v22.214.171.124), Dynamics 365 v8.2 organization with Universal Scheduling Solution
With the goal of continuously improving quality, performance, usability, and responding some customer feature feedbacks, we recently released an update for Dynamics 365 for Field Service, Dynamics 365 for Project Service Automation, below are the new capabilities and bug fixes introduced in this update.
Below are the major bug fixes for this upgrade release
NOTE: This upgrade release can only be installed/upgraded for Dynamics365 v8.2+ org with Field Solution (v126.96.36.199 or earlier)
NOTE: This upgrade release can only be installed/upgraded for Dynamics365 v8.2+ org with Project Service Automation (v188.8.131.52 or earlier)
Performance Improvement on below areas
NOTE: Enhancements and bug fixes for Universal Resource Scheduling apply for both Field Service and Project Service Automation as well as other schedulable entities on Dynamics 365 v8.2 organizations
For more information:
Dynamics 365, Field and Project Service Team