Continue Reading Pieter Veenstra’s Article on their blog
2 ways to duplicate SharePoint Lists to support your Power Apps
Recently I’ve been asked quite a few times to duplicate SharePoint lists as part of creating a Development, Test and production environment in Power Apps.
Blog Syndicated with Pieter Veenstra’s Permission
]]>Nesse curso vamos aprender os conceitos e vamos criar um projeto do zero utilizando Power Apps e SharePoint.
Adquira meu curso na Udemy e aprenda SharePoint, Power Apps e Power Automate do zero.
https://www.udemy.com/course/aprenda-sharepoint-do-zero-com-foco-no-negocio/?referralCode=34B700C89A7463BD0A00
Quer aprender SharePoint Framework(SPFx)? Adquira meu curso na Udemy e aprenda a criar aplicações SPA.
https://www.udemy.com/course/desenvolvendo-para-sharepoint-com-spfx/?referralCode=26879FEB3B350B408792
Seja membro deste canal e ganhe benefícios:
https://www.youtube.com/channel/UCUuAtzt0pMmnC54UpEVls8g/join
Participe da nossa comunidade no Discord
https://discord.gg/PzuuN5N
Let’s connect:
Linkedin: https://www.linkedin.com/in/saulosoaresoliveira
source
First of all: The timesheet app I'm using, is a sample from the awesome April Dunnam | LinkedIn. You can find all the details here:
After deciding which app you would like to add, log into Dynamics 365 HR.
In the main dashboard, search for Employee self-service, there is a chance that is called only Self-service in your environment.
Employee self-service will open displaying the following view.
Right-click somewhere near the Summary section and select Personalize as shown below.
After selecting Personalize, the system will ask you where you want to add the app. Follow the instructions below if you want to add it as a separate tab, which is what I highly recommend.
A new tab will open, select the three dots.
And then select Add an app.
You could either choose a website or a Power App, as you know, we will add a Power App.
Go to make.powerapps, select Details on your app and then copy the App ID.
Go back to Dynamics 365 HR and enter the information as shown below including the App ID.
Once you select Insert, a new tab will display the newly added Power App - or Web if you choose to go that way. Users accessing the app can perform the actions required. However, license implications may apply.
]]>The post Streamlining Course Management in Dynamics 365 Human Resources with Power Platform appeared first on Parag Chapre.
]]>The post Enabling Virtual Entities in Dynamics 365 Finance and Operations Using Power Automate appeared first on Parag Chapre.
]]>First, this is what I am referring to. Your form submission has a Failure result, with the description showing that the target entity (Lead or Contact) could not be created. Before you go any further, make sure that the Form is owned by someone with the right permissions, and check this out if you are not sure.
Usually the first indication something is wrong is seeing the Number of failed submissions in red at the top of one of your forms in the marketing app.
In reviewing the submissions tab, you will then see this wonderful description. How do you figure out why this happened?
First thing, you will need to go to the System Settings panel which is in the Advanced Settings area (or legacy settings if you access it via the Power Platform Admin Center. Then go to Settings > Administration > System Settings. Then click on the Customization tab. Check to make sure the logging to plug-in trace log is enabled. Then close out of this window.
If you needed to turn it on, you might need to refresh a few times, but you should then be able to access the Plug-In Trace Log section.
You might want to create yourself a custom view first of all, but make sure you have this window open so you can quickly find the right log file. The Message Name on the log you are looking for is msdynmkt_createentityfromsubmission.
Now you need to cause a new log file to be created so you can review the issue. Go back to your marketing form and select one of the form submissions, then click the Resubmit button at the top.
Now go back to the Plugin Trace Logs and you should see a new one generated. Go ahead and open that then scroll down to the bottom of the Message Block. It’s likely that the last couple of lines will give you what you are looking for. The key bit for my issue is ‘Attribute ‘address1_city’ cannot be NULL’.
Now I don’t have the City field required on my Lead table… so what’s up? The next logical thing to consider should always be Business Rules, which most times (and by default) are set to run on the entity rather then only on specific forms. When this happens, the steps to create the Lead or Contact are to get all of the fields submitted then try and create the record, but then if a business rule kicks in, that’s going to stop the process. On my form example, I had Zip/Postal Code on it, so when it’s filled out, that means the business rule below will be fired and PREVENT the Lead from being created.
Turn your business rule off, then try resubmitting the failed form submission. Chances are, it will run successfully. Now you can go and reassess that business rule and figure out if it really is needed, or if some adjustments can be made so it can live in harmony with your Realtime Marketing Forms!!!
]]>Its a leap year with 366 days (I saw a post on LinkedIn mentioning Dynamics 366 !!)
As we reach the end of February we realize that end of Q1 is approaching soon and things have started taking concrete shape for the year both at work as well as personal life. It was a great to have been part of Power Addicts NL talking about Dynamics 365 Employee and Manager Self Service in February 24, you can find the slides from my presentation below. Thanks to all the organizers, sponsor adesso NL and my employer for the support.
Post COVID consulting life is starting to change a little bit with more in person meetings and coffee machine conversations. I do like it and gives more positive energy
I am super proud to share the we have raised 135 euros in the month of February 2024 to support Prinses Maxima Centrum who are on a mission to cure childhood cancer and also provide the best care to the children. I want to thank everybody for suporting our journey making us go a few steps further.
Will you read more about it and support us with a small donation?
Thanks for taking the time read the nocodehr monthly newsletter of February 2024. It is a collection of small knowledge bites that has helped me learn something new from the Microsoft community and information about the past/upcoming community events!
Hope you like it. Stay safe!
Kamal,
Click on the images to access the amazing content from the community!
Want to know more about Dynamics 365 Human Resources, Power Platform, Microsoft Certifications… Stay tuned and subscribe to my blog:
Please support my charity efforts and help beating childhood cancer:
https://www.maximaalinactie.nl/teams/microsoft-dynamics-365-community-worldwide
#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; width:100%;} /* Add your own Mailchimp form style overrides in your site stylesheet or in this style block. We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */Do you think my blog helped you? Then please share it with your network on LinkedIn!
The post nocodehr newsletter – February 2024 appeared first on Welcome to nocodehr!.
]]>Check out the companion video for this post, where not only will you learn about date and time columns, but also some fun facts about Sir Sandford Fleming.
When creating Date and time columns in Dataverse, you have different options:
And then you need to decide if you want user local or time zone independent
When you run your app (in this case, a model driven app) At first glance, the fields with date and time look the same.
However, users might be living and working in different time zones, and will set their personal preferences appropriately.
We’ll then see the difference, even though we did not change the data itself.
If we were to look on a Power Pages website, the times would reflect the time zone settings of the device the web page is being viewed on.
As always… “It depends” ©️
Small things can cause huge impacts. Making a configuration on a date time column early in a process could have big impacts later after a big data migration and go-live. (Again, apologies to those folks in Vancouver who showed up at 6am for a class that was scheduled by a user in Ontario that was really supposed to start at 9am… oops!)
Going to MVP Summit? Consider coming to the Canadian Power Platform Summit in Vancouver, March 15th and 16th.
Cover photo by Windows on Unsplash
Nick Doelman is an independent Power Platform trainer and coach, presenter, Microsoft Certified Trainer, competitive Powerlifter, , former Microsoft employee, once again: Microsoft MVP, and cohost of the Power Platform BOOST! podcast.
]]>If we go through Microsoft documentation we can find out that
Text generation model's capability is a powerful tool in AI Builder. It enables you to quickly and easily build AI-powered applications that use text generated from your input (...). Text generation is powered by Azure OpenAI Service, which is built on Generative Pre-trained Transformer (GPT) technology. These large language models have been trained on a massive amount of text data. This enables them to generate text that's similar to human written text.
At this point, we are all familiar with any of the available generative AI platforms. What I will showcase here is quite similar, but applied to our development scenarios for either Power Apps or Power Automate.
When you log into make.powerapps, under AI Hub you'll see that there's a banner showing: 'Unlock the power of generative AI with GPT'. Select it to move forward.
In the second screen select Create text using custom prompt.
A couple of options will display, select the first one.
A defaulted prompt will appear, I did like the concept the solution was giving, but wasn't sure if the prompt was clear enough, so I re-wrote it a bit. The cool thing about these prompts is that you can add Dynamic content and while testing it simulate what is the content. In the description below I went for the following prompt:
Extract the key takeaways from (Last message) and incorporate insights from (Attached file content) to create a comprehensive summary.
Below you can see the prompt, the two variables, and the button that says Test prompt. I simulated an incoming email and also added some summarized CV information.
You can see below that the analysis and data extraction is very good. It saying to the recruiter, that this person is worth interviewing. Of course, I used it with an HR case, because that is what makes sense to me, but it can be applied to multiple industries and business areas.
After you are happy with your prompt and the results you can save it in this AI prompt library and can use your custom creations for either Power Apps or Power Automate.
If you want to go one step further, have a look at the following two documents:
]]>The post Le rapid learning : définition et exemples appeared first on Change The Work.
]]>What's the difference between applicants and workers for Dynamics 365 Human Resources?
Before starting
If you haven't, just make sure you enable the recruitment management feature. You can easily do that by going to Feature Management > Check for updates > Recruitment management > Enable
Report extraction
Log into Dynamics 365 Human Resources / Dynamics 365 Finance and go to Recruitment management.
A quick tip: After activating the Recruitment management module, I recommend adding it to the favorites tab, it will save you a lot of time.
Once you are in, scroll to the bottom until you find Applicant's resume report.
After selecting the applicant resume report, a new tab will open and you can select a couple of things as shown in the picture below.
When you are happy with the parameters and configuration select Ok. It will take a moment or two to extract the data, but once the process is done you'll get something great like this:
https://video.wixstatic.com/video/135432_48f02044c60d444abdd82846ed92b7cc/720p/mp4/file.mp4Export the report
Once you run the report, you can extract it into different formats. Just select the one you want and the system will export it.
In a nutshell, the Applicant resume report feature in Dynamics 365 Human Resources is a game-changer for HR peeps who want to find the perfect fit for the job. With this tool, you can easily extract a report for all applicants in the system based on different parameters like experience, education, and positions. It takes the data right from their resumes, so you don't have to spend hours going through each one. This means you can quickly sift through a pile of applicants and identify the ones who are most likely to fit the bill. So, if you want to save time, reduce errors, and up your recruitment game, give the Applicant resume report in Dynamics 365 Human Resources a try. It's a no-brainer, really!
]]>Let's start with the basics, what is Power App Cards? According to Microsoft documentation:
Power Apps cards are micro-apps with enterprise data and workflows and interactive, lightweight UI elements that other applications can use as content. Because they're part of the Power Apps ecosystem, cards can add business logic through Power Fx and integration with business data through Power Platform connectors. Using cards, you can quickly build and share rich, actionable apps without any coding or IT expertise.
One thing you need to know before jumping into creating cards is that these are under preview, which means you can have early access to the feature but you might find some difficulties along the way.
The card I'm about to share was created to present at Cloud Technology Townhill Tallinn 2023 in a session I delivered with Yannick Reekmans. This is the documentation used to create the card: Create a card with data from Dataverse (preview) - Power Apps | Microsoft Learn.
What is this card for? To help users update account names automatically integrated with Dataverse. If the user changes the name of the account, this change will reflect in the Table 'account' from Dataverse. ,
Before starting
2. Add a variable: for this specific card, the variable will be EnteredAccountName.
Screens
This Card will have four screens:
A. Main
B. Details Screen
C. Thank you
D. Bye
Components
A. Main
The main screen it's the first one the user will see. In this screen we have the following components:
2. Second text label:
3. Text input:
4. Button:
This is the formula for the button OnSelect:
Set(EnteredAccountName, AccountName); Navigate(DetailsScreen);
B. Details Screen
The details screen it's the second one the user will see. In this screen we have the following components:
2. Second text label
This is the formula:
LookUp(account, 'Account Name' = EnteredAccountName).'Account Name'
3. Third text label
4. Fourth text label
This is the formula:
LookUp(account, 'Account Name' = EnteredAccountName).'Account Number'
5. Text input:
6. First button:
This is the formula:
Patch(account, LookUp(account, 'Account Name' = EnteredAccountName), { 'Account Name': NewName });Navigate('Thank you');
7. Second button:
This is the formula: Back()
C. Thank you
The thank you screen it's the third one the user will see. In this screen we have the following components:
2. Second text label:
3. First button:
Formula: Navigate('main');
4. Second button:
Formula: Navigate('Bye');
D. Bye
The bye screen it's the last one the user will see and it's completely optional. On this screen. we will only have 1 component: an image. You will need the URL of the picture to add the image to the card.
After following the steps, you can add some fun to the card. I want to add a nice background image so you are able to deliver a better user experience. This is what the card looks like:
https://video.wixstatic.com/video/135432_d5364ddee63641109f332c676c2d8445/720p/mp4/file.mp4]]>The feature is called ‘Years of service calculation’ in the feature management workspace.
If you’re tracking service dates for anyone whose continuous service date isn’t their employment start date in the current legal entity, you need this feature. This is about the number that’s shown on the right hand side of the header, either on the new (‘streamlined employee entry’) worker form or in the People workspace. Previously, this number could only be based on their employment start date – meaning anyone who had transferred between entities of the same business, or who you were recognising previous service for after a transfer in under TUPE (or equivalent, for you non-UK folks), would not have the right number showing.
Enabling the feature allows you to select which date the form uses to calculate years of service. With the option to choose from employment start date, seniority date, or adjusted start date. Given that seniority date is attached to the worker themselves and not any particular employment in any particular legal entity, that’s potentially very helpful.
Enable the feature in feature management (remembering you might have to hit ‘check for updates’ to get this one to appear – especially if you haven’t been in there for a bit).
A new parameter then becomes available in Human Resources Parameters. It’s on the ‘general’ tab under ‘Years of service display’:
Hit save, do a browser refresh for luck, and you should start to see the impact of the change pretty quickly.
A couple of things:
Don’t make my mistake and assume that because you’ve picked seniority date once, the number will suddenly be visible regardless of your operating entity. Remember that because it’s found in Human Resources Parameters (and not shared parameters) this setting is legal entity specific. If you’re in GBSI, looking at a worker who’s not employed there, and you don’t see a value – check you set that parameter to seniority date in GBSI. This is the voice of confused experience.
This is obvious – but remember that seniority date isn’t a mandatory field, and it might not be populated. If there’s no data there, clearly there’s nothing to base the service calculation on.
The post What’s new – ‘fix’ that years of service figure appeared first on tomelliott.co.uk.
]]>