We have recently purchased Dynamics 365 for Human Resources (in the cloud) and want to use this to manage our recruitment process.  

We have previously used the PeopleHR Applicant Tracking System (ATS) so it is this kind of functionality that we would like to use within Dynamics 365 for Human Resources.

All my searches have drawn a blank.  It is almost like this functionality was available with Dynamics 365 for Talent Attract and this has been discontinued with no replacement functionality available in Dynamics 365 for Human Resources?

Any advice or guidance provided would be much appreciated :-)

Many thanks

Barry

Blog: https://www.d365geek.co.uk
Twitter: https://twitter.com/D365geek
LinkedIn: https://www.linkedin.com/in/mattcollins-jones
Email: dynamics365geek@gmail.com

source

The post Excel Online (Business) Actions: Create Table – YouTube appeared first on 365 Community.

Continue Reading BIPIN KUMAR’s Article on their blog

{Dynamics CRM Error} The formatter threw an exception while trying to deserialize the message

Today while working one of the queryexpression code in my project I faced this issue. Error Details Message=The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://schemas.microsoft.com/xrm/2011/Contracts/Services:request. The InnerException message was ‘Error in line 1 position 1836.

Blog Syndicated with BIPIN KUMAR’s Permission

The post {Dynamics CRM Error} The formatter threw an exception while trying to deserialize the message appeared first on 365 Community.

To share variables over multiple repos, you can create a variable group, and use that variable group in multiple pipelines.

Quite Easy! But …

Thing is –…

Continue Reading waldo’s Article on their blog

Use Azure KeyVault in AzureDevops for sharing licensing and other secrets

You are probably aware on how “secrets” work in AzureDevops. In a way, it’s simple: you can create variables, and store the value of the variable as a secret or not, simply by tapping the “lock” when creating a variable. To share variables over multiple repos, you can create a variable group, and use that variable group in multiple pipelines.

Blog Syndicated with waldo’s Permission

The post Use Azure KeyVault in AzureDevops for sharing licensing and other secrets appeared first on 365 Community.

Microsoft Teams opera cómo hub de colaboración interna y externa, nos hace la vida más fácil porque disminuye la carga operativa en la cotidianeidad.

Ya sabes que te ayuda a comunicarte, compartir y trabajar con otros, pero; ¿sabes todas las posibilidades que tenes?

Existe un mar de aplicaciones que están diseñadas para acompañarte y adaptarse a tu forma de trabajo. La tecnología Microsoft tiene eso, se adapta a vos y no al revés, debo decir que me encanta.

Para acceder al market de aps tenes que hacer click en el sector de Teams que está marcado en verde: Aplicaciones.

Tenes diferentes categorías para explorar:

• Aplicaciones personales: para ver todo lo que se está haciendo en distintos equipos.
• Bots: ayudan a buscar y compartir información procedente de diferentes aplicaciones.
• Pestañas: para anclar contenido en la parte superior de un canal (Power Platform por ejemplo).
• Conectores: envían las notificaciones directamente a un canal en el que todos pueden verlas.
• Mensajes: compartir contenido enriquecido en conversaciones.

Pero la categoría que más me interesa compartirte es Recursos Humanos, hoy existe la posibilidad de conectar Microsoft Teams con comunidades de Yammer. Conectan la organización, permitiéndote involucrarte con líderes, ver eventos en directo y estar al día de las noticias y los anuncios. Las comunidades también permiten a los usuarios compartir conocimientos, formular preguntas, obtener respuestas y crear relaciones entre equipos y silos de la organización.

When D365 HR first launched as D365 Talent, database logging wasn’t an option. In the multi-tenant world that was new to those of us with an AX background, there was a fear that database logging would result in ‘noisy neighbour’ situations, and greedy data loggers would start hogging resources in a way that would impact on other users.

It seems though that at least some of those concerns have been overcome, because database logging is now generally available via the feature management workspace.

What does that mean in English?

Sometimes changes get made in the system and you need to know when and who by. In my increasingly dim and distant SAP past, we used to have a whole transaction code for it. You could go in and check for table edits that had been made and which user account they were recorded by. It didn’t tell you why they had been made, but at least you could track that user down and interrogate them for more info. Very handy.

There has always been some capacity for this in D365 HR, if you knew how to use ‘manage changes’, ‘personnel actions’, and the table browser effectively. But accurately monitoring certain fields for all updates, or certain tables for all actions including deletions, was actually quite tricky. There were workarounds if you knew the right techies, but it wasn’t part of the standard product.

Now it is.

How do I get my hands on the magic?

Get yourself into the feature management workspace (System administration > Feature management) and find the feature named ‘Database Logging (Auditing)’. Enable it in the right hand pane. I always follow the enable click with a browser refresh, just because it makes me feel more confident that the feature is fully available to me. Once you’ve enabled, you can go and set things up.

How does it work?

First of all you need to have a good long think about what you actually need to track. Noisy neighbour situations might be apparently dealt with (or this feature wouldn’t be in the wild) but you can still create a bit of a monster if you’re not careful. You could track every single field in the database, but it would be a very very bad idea. Think about it. Every time you edit a field in a table, you’re doubling the number of changes that have to be made to the database. Not only are you making the change, you’re also writing a record of that change into the sysdatabaselog table. That table is going to get huge very quickly, so you need to give some consideration to:

• What you actually need to track (clearly not everything, so which fields and tables really matter to you)
• How long you need to keep the history for (when are you going to clear that sysdatabaselog table)
• Whether you might need to create a backup of that table periodically

Once you’ve had a good stern word with yourself and tempered a natural tendency to want to log every single thing, you’re going to go and use the database logging wizard to set up monitoring on your most important fields.

To do so, jump to System Administration > Links > Database > Database log setup.

First, unless this is the first time anyone’s accessed this page, you’re going to see a grid which shows which tables or fields are being monitored. Presumably the field you want to add isn’t already here, so click ‘New’ on the ribbon.

The database logging wizard shows up, with a nifty little progress bar to show you how many steps are included in the process (I can think of MANY other places where this progress bar could be handy, but that’s one for another time). Read the instructions and follow them by clicking Next to continue).

Now you’re going to see a screen which lists the tables and fields in the database, and you’re going to select the ones you want to track. If you’ve ever seen the old AOT in previous iterations of this product you’ll be having flashbacks here – but don’t worry, you’re not missing out if this is completely new to you.

Now, it might just be me, but I find it easier to work in technical field names rather than the plain English ones, which is the only way I feel sure I’m looking at the right thing. On that basis I always check the two boxes at the bottom to ‘show all tables’ and ‘show table names’. This expands the list and gives you first the technical name and then the plain English name of whatever table or view you’re looking at. Admittedly it looks a bit more complicated, but I actually find it easier to work with that way.

When selecting what fields you want to track, it helps to know exactly which table that field resides in. So here’s a tip that can help you identify the table location of any value. Let’s say I want to know the table that the job function field resides in (yes, I’m a sad case, and I know this by heart, but let’s pretend I haven’t spent the last seven years of my life committing the table structure of this system to memory).

• Find the field in a form
• Right click the field so that you see the ‘form information’ option pop up, and click on the form name to open the form information form (not a confusing sentence at all)
• Open up the ‘administration’ tab
• Find the ‘Control name’ option – that should be TableName_FieldName – so for job function I see HcmJobDetail_JobFunction, telling me that to track this field I need to find the table called HcmJobDetail in the list.
• This is where it helps to have checked the ‘show table names’ option in the wizard, because then the table list is sorted alphabetically by technical table name, and there’s no guesswork involved.

Now you can work your way down the list choosing which fields to monitor.

At this point I feel like it’s important to make a good practice point. Database logging shouldn’t be about shutting the stable door after the horse has bolted. Your first step to avoiding unwanted data changes in your database should be configuration of good security roles that are appropriate for your business. If you don’t want your average HR administrator to be able to edit the jobs, take that privilege out of the standard role. Don’t track every single change to the job table just in case somebody does something you asked them nicely not to, but never put anything in place to prevent them doing so. There’s always one user who doesn’t quite listen in training, presses random buttons just to see what happens, and then inadvertently causes problems. Take steps in advance to prevent that happening.

In the third step of the wizard, you’ll see a list of existing fields or tables being monitored, and any new selections you made at the previous stage. Worth mentioning here (in case you’ve spent ages trying to select a checkbox and can’t seem to get it clicked) that:

• At the table level you can track for all changes – records created, edited, or deleted, as well as renamed keys.
• At the field level you can only check for updates.

If there’s nothing in the ‘field label’ column, that’s monitoring the whole table, and you can track for everything.If there’s something in the field label column, you’re looking at a field, and so the only box you can check is the updates one.

Once you’ve selected everything you want to track (and yes, you can return and change this later if you need to add or remove something) you can hit next to move on to the last stage. This stage is just a confirmation table which has you check the number of changes you want to make to what you’re tracking. Barely even worthy of a screenshot, but I’ll throw one in anyway.

As soon as you’ve hit finish, you’ll start to notice that transactions which you’ve asked to track are hitting that sysdatabase log table. There’s nothing more to it than that – they just start queuing up. Remember I said that table would get bit quickly? It’s a little bit scary just how quickly that happens.

So how do I actually use it?

Enabling the feature adds another menu item, which doesn’t appear to actually exist in the links page (must be an oversight and will surely be fixed at some point, but for now this is true) – which is Sys Admin > Links > Inquiries > Database log. Use the search bar to get there instead (just type in ‘database log’.

The grid shown is a slightly nicer view of the sysdatabaselog table than you get purely through the table browser. You can click on the ‘history’ tab to see repeated updates to the same table, what the previous data was, what the new data is etc.

Why should I switch it on?

We’re all friends in HR, and we all know that sometimes you need to know who changed a field. Not everyone is decent and law abiding and being able to track who changed whose salary record (among other things) is a good thing. On that basis, you should definitely give some serious consideration to enabling this feature on key fields like that.

The post What’s new – Database logging is go appeared first on tomelliott.co.uk.

So first, the old way of getting to the Email Signatures. This is done by either going to Advanced Options, then Settings, then Templates, then Email Signatures and adding a new signature from here:

Or, a user can go to Personal Options, then Email Signatures, then add a new signature from here. Either way, I think we can agree, it’s a bit ugly and clunky. And yes, you can still add images and hyperlinks this way, but it’s not obvious or intuitive, and once they are added, it’s not something you can edit easily.

Now let’s look at the nice way in the Unified Interface. If you are using the Customer Service Hub app, they are right at the bottom of the Service area.

We can add the link to the Email signatures to any other app by simply editing it. This should of course be done in a SANDBOX environment first and added to a Solution, then imported in to your PRODUCTION environment. To edit, the easiest way would be to add the Site Map to your solution, or you can navigate to the sitemap by clicking on Edit from the App.

Then from the app, click the Edit icon on the Site Map.

Add a new Subarea to the Group where you wish to have the Email Signatures accessed from.

In the Sub Area, simply select Entity as the type then search for Email Signature. The icon will be set to use the Default image for that entity, and you can change the title if you wish.

Now we can see the Email Signatures have been added to the app.

Now adding and editing the signatures is easy. We give it a name and then can set it as the default. This means the signature will be added automatically to all new emails created by the owner of the signature.

Add a new one, and now you can see an icon to add a hyperlink, and an icon to add an image. We can also add an image with a hyperlink at the same time. Clicking on the image icon we can add in a new link to a social media profile.

We can add an image either from a URL, or browsing out and adding an image that way. Both work fine, but from a marketing perspective, an organisation may choose to set up the images using a URL. The images can then be swapped out directly on the server if needed rather than having everyone manually add in new images later on. We can then set the target URL, with the link opening up in a new window, and then set Alt text (in case the image doesn’t load) and then the width and height of the image.

Now we can see the images in the signature. You can then save and close your new signature.

One thing that also STILL works (as detailed in the original post about this from 2017) is the ability to copy and paste images in to the signature. This is my signature in Outlook in Office 365. I can simply copy the entire thing.

Then I can just paste it directly in to the Signature editor in Dynamics 365.

Then when I create an email in D365, the email signature is appended to the bottom of the email.

Wondering if the images will show up? Here you can see the email that was sent from D365 to a Gmail address. All images are present and accounted for

The post Enquête : Quel impact le covid-19 va-t-il avoir sur le recrutement de talents internationaux ? appeared first on Change the work.

This morning though I saw a conversation on a Yammer site about org charts, and I thought it might be worth flagging this up just in case it’s of use to anyone.

In Teams, there exists a little app called ‘Who?’, and its pretty great.

What does it do?

There’s one key thing that it does really really well – and that’s make your org chart accessible to your average user in a visually engaging, appropriately secure, way. I get asked a lot by D365 HR users how they can make the built in org chart more visible to their workforce. And there are ways of doing it that involve a few security tweaks to expose the right pages to the right users. But frankly, I like this app better. For one thing, it sits in Teams, so I don’t have to go and log in to a separate product to get to the information I need (even with the abject joy that is single sign on, I’m too lazy to switch products). By pinning the app to my left hand navigation bar in Teams, I can jump straight to my org chart info with a single click.

The app consists of three tabs (plus the ubiquitous ‘About’ section):

‘Chat’ allows you to interact with a bot and ask questions about your org chart info. Acceptable questions include:

All of the above surface a list of contact cards by way of a search result, which you can click through on to message, email, call or check their position in the org chart.

‘Your org’ opens a visual org chart with the logged in user as the starting point of focus. You can either move up or down and around the org chart or search for a particular user. My only complaint about this view is that without clicking on a contact card, there’s no indicator that the user has any direct reports (think how D365 HR indicates that there’s an org layer below each worker with a solid black line at the bottom of the worker card).

‘Forthcoming meetings’ looks up against your calendar, and shows contact cards (featuring name, job title and a photo) for everyone in your upcoming meetings. Clicking on that card pops up the more detailed version with full interaction options for that user. Worth noting though that these cards are only populated for users on your tenant. So for external users, you just see a name.

Any drawbacks?

Weeeeell, there’s the classic one – in that the whole app reads from data in Azure Active Directory, so to get the best out of the Who app AAD has to be up to date and accurate as far as HR is concerned. More often than not I find that AAD is a bit behind HR – particularly when we’re talking about who manages who.

Of course, if you’ve got the right techies around, you can set up an integration between your HRIS and AAD, in which case it’s more likely that everything will be in sync. If you use D365 HR, or something else that’s plugged in to CDS, there are Power Automate connectors that can help this happen. Even better, there’s a little something on the release plan for this year that might just make that integration a little bit easier.

Where can I get it?

Open the Teams desktop app and click the three dots at the bottom of the left hand menu. In the ‘find an app’ search box type ‘Who’, and then click the app tile that appears. Right clicking on the app tile gives you a ‘pin’ option, which adds the app permanently to your Teams navigation bar.

The post Who? Navigating your org chart in Teams appeared first on tomelliott.co.uk.

You can check out the video on YouTube!

Many-to-Many Fields and Canvas Power Apps

I was working with a client on a canvas-based Power App and we needed a way to quickly tag one or more categories to a specific Account record. We are using the Common Data Service as our data store (of course!)

I work pretty much exclusively with Power Apps connected to the Common Data Service. The Common Data Service provides a robust solution for not only storing data but also security, flexibility, automation and extensibility.

While I could have created a multi-item optionset, the list of categories were going to be constantly updated so it was a better approach to use a many-to-many relationship and a custom entity to hold our category options.

The issue is that if you just add a many-to-many field to a canvas Power App form, you will get a litany of error messages as forms and DataCards aren’t fully able to implement the features of the many-to-many attribute in the Common Data Service.

The following is a series of steps and a solution to allow your users to add multiple related records to a record using a form on a canvas Power App.

The Solution

Lets take a step back and walk through the whole solution. Let’s assume that our requirement is the flag the Common Data Model Account entity with one or many different category tags. We also want to be able to edit and add to these tags on a regular basis.

I created a custom entity called “Category” that had a name field.

I created a N:N relationship between Accounts and the custom category entity, so we can “tag” Accounts with many different categories.

I began to add a series of categories (colours) but these could be anything (preferences, industries, etc).

In a model-driven app, we can easily add or remove “categories” from records using the model-driven user interface. This doesn’t require any extra special coding.

Adding Categories on a Canvas App

I created a simple canvas Power App that will perform the following;

• View existing Accounts
• Add a new Account
• View the details of an existing Account

Implementing a many-to-many relationship on a canvas becomes more difficult. I could create a couple of galleries and assign the various options as outlined in this Microsoft posting. However, I would like to keep the interface relatively clean and easy to use.

As I mentioned earlier, simply adding the many-to-many lookup field will result in errors.

I tried to work through the issues and ran into problems. Thankfully a call to the MVP hero brigade resulting in the following solution from Hardit.

First thing is to set the Items to the category entity on the Categories DataCardValue. (Note: You will need to unlock the control).

Then change the Display mode of the Category DataCard from “View” to “Edit”. Since the Form cannot natively handle updating many-to-many fields, by default it will be set to view mode.

Then clear out the Update property on the Category DataCard, as it doesn’t have the ability to properly update a many-to-many relationship between two different Common Data Service records. (We will get to that soon).

Normally I would add a formula to a button to submit the form which would create a new record in the Common Data Service. However, I need to do some extra steps to relate the many-to-many selections;

I still add a button to save my data, but will need to add some extra code beyond the simple form submit.

And then we add the code.

Here is the full formula for the save button:

ClearCollect(
   collectcategories,
   DataCardValue4.SelectedItems
);
SubmitForm(Form1);
Set(
   newAccount,
   Form1.LastSubmit
);
ForAll(
   collectcategories,
   Relate(
      newAccount.Categories,
      ThisRecord
   )
);
NewForm(Form1);

Here is a breakdown of what each line of code is doing:

The ClearCollect gathers the selected items (the many-to-many references) and adds them to a local collection.

The SubmitForm will save the new Account record to the Common Data Service. Since we cleared the Update property, you will not get an error from the Categories field.

The Set command simply assigns the newly created Account record reference to a variable that we will use with the Relate function (next step)

We will then loop through each record in the collection (the many-to-many references) and then call the Relate() function to link them to the newly created Account record.

Finally we will reset the form to add more Accounts.

Testing the App

When I run the app, I see the various selections and can assign them to the account, just using the combobox control on the form.

I then click the save button (the checkbox) and the record saves to the Common Data Service.

If we look at the record in a model-driven app, we see that the categories (colours) were related to the record.

If you add a read-only form and view the results in the canvas app as well. You should be able to work with this solution to add the ability to “unrelate” the corresponding records as well. (Consider that your homework!)

Summary

Many-to-many relationships to reference entities can be extremely helpful and actually I like the implementation on the canvas app better than the model-driven app. However for model-driven, there are PCF controls that replicate this functionality (see the PCF.Gallery for examples).

Again, thanks to Hardit for his help. Definitely check out his blog and follow him on twitter for some great Power Platform tips and techniques!

Cover Photo by John Barkiple on Unsplash

Phone Photo by Fredrik Solli Wandem on Unsplash (modified to add MVP logo)

Nick Doelman is a Microsoft Business Applications MVP and is presenting at DynamicsCon on September 9th as well as UG Summit in October. Follow Nick on twitter at @readyxrm

• A revamped customer journey designer experience.
• Microsoft Teams integration for webinars
• Improved social posting and analytics
• The ability to use natural language to create segments

What are the features and when will they be in Public Preview (PP), what will be in Early access (EA) and when will they be General available (GA)? Keep reading.

Use continuously updating, multidata source segments from Customer Insights in your marketing campaigns – GA October ’20

The important integration with Customer Insights keep getting better. From October marketers can see the segment creation logic and discover CI segments instantly. The segments from CI are automatically updated, but can also be saved static segments in Marketing. The marketer can now also choose if they want to use native Marketing dynamic segments or CI segments in a customer journey. Better flexibility for the marketer and a very good way of utilizing the dynamic Customer Insights segments!

Create customized emails faster – EA August ’20. GA October ’20

The email editor will be improved, you now don’t need to use HTML as much. You’ll be able to add more than three columns to the email, better support for Outlook rendering and improved email editing performance, including faster loading and element interaction.

Collect data from form submissions more easily with expanded entity
options – EA August ’20. GA October ’20

Yes, yes, yes, yes! I’ve been waiting for this! Marketers now get the ability to collect form submissions and store them under another entity! They can now manage form submission data as they want, and create workflows to store the form submissions as any other entity. Gone is the restriction where you need to connect a form to a Lead or a Contact.

Run webinars and meetings using direct integration with Microsoft Teams – EA August ’20. GA October ’20

Yet another BIG feature from the Marketing team. Marketing now includes a direct integration with Microsoft Teams live events and meetings! Marketers can create and host live events with Microsoft Teams as the webinar provider. Webinar are setup as a Teams live event or a Teams meeting, these can then be integrated directly into Marketing events. Who doesn’t love Microsoft Teams!

Build customer journeys more efficiently using the new canvas experience – EA August ’20. GA October ’20

The Marketing team has completely redesigned the customer journey canvas, they’ve made it more intuitive and efficient. Just look at this list of features

• Enhanced performance and reliability when building complex, multi-step journeys
• Simplified time-related journey actions
• Negative journey paths!!!!
• Horizontal and vertical views

Create and manage content-rich social media posts and easily monitor performance – EA August ’20. GA October ’20

Redesigning and making things work even better seems to be core to this release of Marketing. That’s also what they’ve done with the social posting, redesigned the post creation experience and the scheduling experience.

Use natural language to create targeted segments – PP October ’20

This feature is only coming in Public Preview in October, with no GA date. With this you can use simple words to specify the attributes and logic for segments, so you can find the exact audience you want. You can create the segment of “customers who live in Norway, but not in Oslo and work in tech.”

Read the full release notes on Dynamics 365 and on the Power Platform.

This release the Dynamics 365 Human Resources team are focusing on these five areas:

• Transform the employee experience
• Build an HCM ecosystem
• Optimize HR programs
• Unlock your HR data
• Enrich your existing Microsoft solutions with HR data

Let’s dig in to all the features and when they are in Public Preview (PP) and when they are General available (GA)

New entities in CDS

They continue to work on getting entities into CDS from HR, here are the new entities and when you’ll find them in CDS. This means that there are even more entities that you can use together with the Power Platform.

• Benefits management – GA October ’20
  This will help you with integration to your payroll and benefit providers.
  • Setup entities
  • Benefit plan entity
  • Worker enrolled benefit entities
• Skills and certificates – GA October ’20
  Finally, we can use this information in other Dynamics 365 applications that use skills and certificates, like Field Service and PSA/Project
• Scenario-specific APIs – PP September ’20, GA October ’20
  I look forward to seeing how this will work and how we can integrate closer with recruiting solutions.
• Performance entities – GA November ’20
  With the performance entities in CDS you can now do integration, reporting and extend it with for example a Power App.

New stuff

Custom links in Manager self-service – GA December ’20

You can add links to the manager self-service page the same way as you can do in the “My information” tab in Employee self-service page.

Manager access to employee attachments – GA February ’20

This is a feature I really thought was already there. But now managers can get access to documents that employees and HR have uploaded.

Employee Leave and absence experience in Microsoft Teams – GA October ’20

This is a cool feature that I’ve tested and blogged about, getting ready for GA in October.

Automated address validation – GA October ’20

HR will now verify alternate addresses and give alternate suggestions if available.

Integration with LinkedIn Talent Hub – PP July ’20, GA October ’20

This is the integration we have all been waiting for since they deprecated Attract is now finally here! You can test it in July and it will be in GA from October. This is going to help everyone that used Attract and is now looking for a new ATS.

Enhanced candidate profile in Personnel Management – PP September ’20. GA October ’20

Have you ever set up a trial in HR, and you’ve seen the section “candidates to hire” and wonder where they came from? It seems to have been something left from AX, but wasn’t really needed in Core HR because you had Attract. Now that is changing! You can now create candidates in personnel management and include a lot of details about them. All the information about the candidate can then be transferred to the new employee record. Easy and really helpfull.

Manager can submit a recruiting request for open positions – PP September ’20. GA October ’20

A manager that want’s to hire a new employee, can now create a request to recruit which will initiate a workflow. In this workflow you will be able to populate the request form with default job and position information that can also be changed if needed. The managers can also track the status of the hiring process with the recruiter.

Organization and Personnel management workflow experience enhancements – PP September ’20. GA October ’20

The workflow for new hire requests and changes to existing employees or positions will be improved.

Azure AD integration – PP October ’20. GA December ’20

It seems like AAD will be even more tightly connected with HR, which is needed, why would you want to administer users and access any other places than AAD?

Enable simplified integration with payroll providers (Phase 1) – PP October ’20. GA December ’20

This feature will enable partners to use an API for pay roll systems. This will also enable employees and HR professionals to view and update payroll related information through deep linking with SSO!

Leave and absence

• Leave and absence workflow experience enhancements – PP September ’20. GA October ’20
  Employees and managers can update or cancel leave requests.
• Provide additional insight into leave balances – PP October ’20. GA November ’20
  The leave balance insights will simplify viewing of employee leave balances to a single place. It will also give the employee and manager insight into accrual amount, time off taken and remaining time off.
• Cross company view of employee leave for managers – PP November ’20. GA December ’20

The last one for leave and absence is so big and is so important that I want to highlight it;

Approved leave integrated with Microsoft Outlook Calendar – PP February ’21. GA March ’21

When time off is approved for an employee, their Outlook calendar will automatically update – how cool is that!

Create customized reports – PP November ’20. GA December ’20

Oh how I’ve waited for this! This I can’t wait to play with in November. You can create custom reports for human resources, time, finance and other data. AND you can embed custom reports in workspaces.

This is such an amazing list of new and enhanced features and the kind of development speed I was dreaming of seeing once they deprecated Attract and Onboard.

I’m very happy!

Read the full release notes on Dynamics 365 and on the Power Platform.

We get to know more about what they do and how they keep pace with our ever-changing platform, their experience of speaking at events and with imposter syndrome, before moving on to the important stuff: how awesome dogs are.

This episode was recorded on 24th Sept, 2019.

If you’d like to get in touch with Lee, Sara or Matt you can find them on Twitter:

• Sara Lagerquist @lagerquistsara
• Matt Beard @MattyBeard
• Lee Baker @LeeMBaker

Mentioned in this episode were:

• Event: Oct 5th 2019 – Power Platform Saturday Sweden, that Sara is helping to organise
• Event: Oct 15th-18th 2019 – User Group Summit Orlando
• Docs: Dynamics 365 2019 Release Wave 2
• Docs: PowerApps Component Framework (PCF) Getting Started
• Podcast: Emma D’Arcy’s excellent talk on dealing with imposter syndrome (link TBC)