Skip to content

On demand · Product video

Share quality tests and send test alerts in Microsoft Teams with Quality Inspector

For quality teams that work in Microsoft Teams and want to share tests and hear about changes there.

Recorded May 31, 2023 · 11 minutes

Quality Inspector microsoft teams video thumbnail

Summary

Quality Inspector works with Microsoft Teams in a few ways. The video shares an open test to a Teams channel with Share to Teams and configures the fields shown in the preview card from the personal device interface section of the Quality Inspector setup. It mentions adding a Teams tab for assigned or unassigned tests. It then builds a Power Automate flow that runs when a quality inspection test changes, gets the record and its Business Central link, and posts a message to a Teams channel with the test, item, lot, and assigned user.

Key topics

  • Share a test to a Microsoft Teams channel
  • Choose the fields shown in the Teams preview
  • Post a Teams message from Power Automate when a test changes
  • Add the Business Central link and test details to the message
Read the transcript

I’m going to review creating a test and having that test available for use with Microsoft Teams. We’ve already gone through in other videos how to create a test automatically and manually, so we won’t go through that configuration. What we will review is how to use this with the Teams integration. One easy way is the Share to Teams functionality. If we take a look at any of these existing open tests, we can use Share to Teams, and it grabs the URL and makes it available for anybody inside of Teams.

If we post this into the quality inspectors example, you’ll notice that the preview mode is configurable. Those using the phone or tablet interface will be familiar with how to configure it, because in Business Central and Teams it uses the same brick fields that you can configure. We see the grade, test details, and document, and it’s pulling in a whole bunch of other details from our test. If we take a look at Teams, we see that the same link was shared, and if we open it, it takes us into Business Central to that specific record. This is a great way to handle ad hoc communication with anybody in your Teams environment: “Hey, I need you to take a look at this test.”

To configure the fields in that preview, it’s the same fields you configure for your phone and tablet interface. We navigate to the Quality Inspector setup and scroll down to the personal device interface section. You can still configure your caption and include whatever fields you’d like, for example if you had additional source fields you wanted to show, or if certain values didn’t matter to you. Say you always create your tests off an item and a lot, perhaps off lot number information, and your tests aren’t related to a document. Then you could replace these document fields with something that makes sense for you.

One other thing you can do in Teams is add a tab related to your quality inspection tests. For example, you could add tabs showing unassigned or assigned tests, and interact with them entirely within Teams.

Now let’s go through an example with Power Automate to create a Teams notification whenever a test has been altered or created. Any time a test changes, we’ll put a post in Teams so we see that our test has been altered. To get started, we navigate into Power Automate and create a new automated cloud flow. For simplicity, we go with the Business Central trigger for when a record is changed, and we name it Example Teams Notification. We choose our environment and our company, my Examples company, the Quality Inspection API category, and the quality inspection test table. So any time that record changes, we do something.

Next we need the URL, which we can get from Business Central. We find the Business Central actions, and there’s a Get URL action. We put in the same environment and the Examples company. The page is the page ID you want to link to. In our case, I want to open it directly on the card page, so I open the card page, and in the URL you’ll see page equals a number. Grab that number and put it in here; in our case it’s 23067641. Then we grab the row ID, which comes from the When a Record Is Changed trigger.

Now Business Central is telling us what the URL is, and the next step is to post it in Microsoft Teams. We find the Teams action Post Message in a Chat or Channel. We’ll post as the Flow bot, though you could post as a specific user. We’ll post into a channel for everyone to see, though you could also post to individuals. We use our Insight Works example team and the quality inspectors channel. Then we say, “Hello everybody, a test has changed,” and grab that web client URL.

You’ll notice we don’t have a lot of values by default. Business Central doesn’t give you much, so if you want details like who it’s assigned to, we pull them in through another Business Central action to get the record. We configure it with the same details, the table is our quality inspection tests, and the row ID is the same row ID. Now we’ve got fields we can put in the message: who it’s assigned to, a bunch of source fields, and things of that nature.

First we put in the link itself, the web client URL. One little twist is that when you add this in, it’s just text, not an actual link. The trick is to switch into this mode and add it as a link; if you’re using the desktop version it’s a little easier. Then the message says the test number, for the test plan, on the item number, for the lot number, is currently assigned to the assigned user ID, followed by our link. We add a link to the web client URL, show the URL itself so a person can see what it is, and off we go.

Now say we’re in Teams and clicked on the test. Maybe that test was referred to me by someone, but I can still alter it. Perhaps I want to assign it to another individual, but I currently don’t have permission to change that assignment. You can change that permission in the function permissions. For now we’ll make another change: we’ll add “extra detail that is important.” This should trigger the modified record and send our Teams message. Then we’ll change the permission to allowed.

If we take a look at Teams, we see the message because we changed that test: “Hello everybody, a test has changed.” There’s our test document, for the test plan receive, on that item, for the lot, currently assigned to admin. So there are several different ways of using Teams with Quality Inspector. If you’re doing manual link sharing, you’ve got the preview mode. You do need to have the Business Central add-in installed for the preview to work, but it’s all configurable. That’s how you integrate Microsoft Teams with Quality Inspector.

Questions about this webcast?

Send your question and the Insight Works team will reply by email. Ready to plan a project? Contact your Microsoft Partner.

Ask a question

Webcast Questions