Dynamics 365 for Talent – manager recruitment submission extension

[vc_btn title=”Back to the Video Library” color=”warning” link=”url:https%3A%2F%2Fdynamics365society.uk%2Fmicrosoft-video-library%2F|||”]

In this video I prove a demonstration of the new capabilities I have built out in Dynamics 365 for Talent. That allows a manager to submit a new recruitment request from the Employee Self Service work space – this then, after approval, creates a new job in attract and a new position in core HR.

Views: 63, Likes: 2

Go to William’s channel

How to Enable the PowerApps AI Builder

Hey, Will here – just a quick post. I’ve had quite a few people come up to me asking how to enable the new “AI Builder” for Power Apps on their environment – which strikes me as slightly strange as it comes enabled as default. However, here is how you do it.

 

  1. Go to: https://admin.powerplatform.microsoft.com/ 
  2. Then using the navigation pane select “Environments” then select the environment you wish to turn the ‘AI Builder’ on for:
  3. Then select “Settings”:
  4. Then select “Features”:
  5. Then enable the PowerApps AI Builder:

Now go forth and build something AWESOME!

Connect Dynamics 365 Finance & Operations to CDS – new CDS environment, integration, new entities & populations – Article Two

This article is part of a series of articles that is going to run you through setting up the following:

  • creating a new CDS database,
  • creating custom entities within CDS
  • creating an integration from F&O to CDS
  • Creating a new view
  • Exposing this new data within a CanvasApp

Article two of four – integrating Finance & Operations to CDS and creating a new view. Find part one here(!)

Now that we have our entity focused around projects we need to integrate it with Dynamics 365 for Finance & Operations to fill it with some sweet, sweet data! Let’s head over to www.admin.powerapps.com and go to “Data Integration” from within the navigation pane:

From here go to the “Connection Sets” tab and then “New connection Set”:

Give the connection set the name Project, then select your CDS environment and F&O environment – now a key part is stating the organisations you wish to connect. Provide the Legal Entity ID of the Finance & Operations company you wish to connect to and then the ‘org’ name of the CDS environment – found by going to www.admin.powerapps.com then looking at the bracketed (org######) string – this is the  organisation ID

Then go to the “Projects” tab and hit “New Project”:

Provide your project with a name for example “F&OtoCDS” and then select the template “Fin and Ops to CDS” then hit ‘Next’:

Select the connection set you create earlier named “Project” and hit “Next”, then select the “Organizations” grouping you created along side the connection set earlier and hit “Next”. Then agree to the ‘Privacy notice and consent’ without reading it because, well, life is too short to be boring and not take risks – by hitting “Create”!!

You’ll then be greeted by your new Project! But currently it is an empty carcass that is achieving nothing – so hit “Add Task”:

Now, name your tasks “Project”, select the “Projects” data entity from Dynamics 365 for Finance and Operations, select the “Projects” entity you created within the Common Data Service then select the “Organizations” created earlier. Then hit that big GLORIOUS button “Create”.

This will then create the new ‘Projects’ tasks, select the task which will then drill-through to allow us to start mapping between the two entities, map the following and hit “Save”:

Now for the exciting part, let’s execute/”run” this integration and see the data flood in! Hit “Run”! This will now kick-off the integration and take you to the “Execution history” screen

Then you’ll be greeted by the greatest sight of all a big green tick under the ‘Submitted’ column meaning it was successful:

Now let’s go check out that data – head back to www.web.powerapps.com and go to the custom “Projects” entity you created, now before we can see the data using the “Data” tab we need to create a new view, so go to the “View”  tab within the “Projects” entity and hit “Add View”:

Give your view a name and a description (if you’d like too) and hit “Create”:

Now select the fields from the left you want to appear on the view (simply by click on the ones you want will automatically transport the to the view) then hit “Save” then “Publish”:

Then go back to your entity (previous tab within your browser) and hit “Done” which will refresh and bring in your newly published “Main” view.

Now let’s go and check out the results, go to the “Data” tab and switch to the newly created view:

And now you can see all your awesome data (annoyingly i forgot i made some changes to my DE so the name hasn’t come in correctly but yours will be fine):

This concludes part two!

 

Connect Dynamics 365 Finance & Operations to CDS – new CDS environment, integration, new entities & populations – Article One

This article is part of a series of articles that is going to run you through setting up the following:

  • creating a new CDS database,
  • creating custom entities within CDS
  • creating an integration from F&O to CDS
  • Creating a new view
  • Exposing this new data within a CanvasApp

Article one of four – creating a new CDS database and new entity (this is not a deep-dive more of a beginners run through, deeper dives will be created soon(!))

1] Creating a new CDS database:

Go to www.admin.powerapps.com/environments and  select “New Environments” located in the top-right hand corner of the screen, then provide a name, region and environment type as shown below:

Then hit create, a new dialog box will pop-up asking if you wish to create a new database – of course the answer is yes:

The next dialog box will ask for more settings related to the CDS environment, select the currency and language you want it to be deployed in and whether you wish for sample apps and data to be included in your environment then hit “Create database”.

Your new environment will be provisioned, give it some time but it will happen.

Now head over to www.web.powerapps.com so the real work can begin!

First we need to select the newly provisioned environment from the environment drop-down list located at the top of the screen:

Then from the navigation pane on the left hand-side go to “Entities” then ‘New Entity’:

A new dialog box will pop-up – provide this with a relevant display name, it will automate a plural display name but this can be changed if necessary, then a name for the actual CDS entity which cannot be changed once created.

Once all filled out hit “Next” this will spin up the new entity.

It will automatically place you in the “Fields” tab – hit”add field” and we are now going to create a series of these new field starting with “Project ID”. Provide the new field with a display name, name (system name that cannot be changed) and the data type of “Text”:

then hit “done” – now rinse and repeat this AMAZINGGGGGGGGGG process for all the fields show below (Contract, CustAccount, Customer Name, ProjectName):

Once you have completed all that hit “Save entity” and…

VOILA your first entity is created and thus completes the first article in this series! Click here for part two (which runs through integrating F&O to the CDS)!

How to create resource in azure: Cognitive Services & PowerApps Part two

This is a carry on from How to create resource in azure: Cognitive Services & PowerApps Part one.

So now we have the “Text Analytics” resource setup let’s create the CanvasApp PowerApp, head over to web.powerplatform.com and select apps- then import package, import the Text Analytics Canvas app from our TDG PowerPlatform Bank by clicking here!!!

Once the app has imported and you have opened it  go to – “View”>”Data Sources”:

Select, at the top left of the pane that opens, “+ Add Data Source” then “+ New Connection”,  then search for “Text Analytics”:

Then select “Text Analytics” then it will ask you for the “Account Key” & “Site URL” (which is actually the Endpoint URL), this can be found in Azure. Go to Azure, All Resources, then Select the “Text Analytics” resource you create in step one .

Then select either “keys” from the ‘Grab my keys’ main grouping or “Keys” from the Navigation pane “Resource Management” groupings:

Then copy your first key:

Then paste that back into the PowerApp Data Source under “Account Key”:

Now to grab the URL Endpoint, head back to Azure – go to “Overview”:

Then copy the “Endpoint”And paste that back into PowerApps in the “Site URL” field:

Then hit create.

Now you’re ready to use the app – explore the formulas and controls used, you’ll find it’s easy to replicate. If you have a question comment on this blog or reach out to William Dorrington directly via LinkedIn.

 

 

 

How to create resource in azure: Cognitive Services & PowerApps Part one

So you’ve seen all this discussion around Cognitive Services and now want a piece for yourself – you open your computer, you down a coffee and now you’re thinking “what now”?

Well don’t worry, I’ve got you!

Let’s start with Text Analytics, crack open Azure (https://portal.azure.com/#home) and select “Create a resource”:

Then in the search bar search for “Text” and then select “Text Analytics”:

Then select “Create”:

Then enter the following; Name, Subscription type, Location (locations of where the resource will be held), pricing tier and resource group allocation (for filtering and searching properties). Once happy select “Create” and you’ll be notified when the resource is ready.

Once it is completed it will be available via the notification of completion message (via link) or in “All Resource” (from the navigation pane to the left hand side of the screen), then look for “TextAnalytics” or whatever you named your resource. From here you can view your “Keys” or if you need the endpoint URL select “Overview” and then you’ll see a URL under the category of “End point” e.g. https://uksouth.api.cognitive.microsoft.com/text/analytics/v2.0 (the URL only changes dependant on the location you selected e.g. https://[location].api.cognitive.microsoft.com/text/analytics/v2.0).

Now to create the PowerApp data source, find part two here..