Ultimate Polling and Quiz Experience with Polls app: The Replacement for Forms app in Teams meeting
Initially Forms app was launched in Teams - for different experiences based on the sync vs async user scenarios, as it points to polling experience in meetings for quick creation to launch, while it points to survey experience in the context of Teams channel.To provide an intuitive and easy-to-access experience , Polls app was launched - a dedicated app for all your polling and quiz needs in Teams meeting and chat. We are glad to see that hosting an effective and interactive meeting just got easier after the launch of Polls.
Microsoft Forms: Multiple Choice Type is not showing all answers in SharePoint List
Hi, I have created a Microsoft form which contains a field "Pemohon". This field is a VLOOKUP of the type "Multiple Choice". The entries submitted in this form are reflected in the SharePoint list. After submitting the form, the multiple choices entered in the field are not visible in the SharePoint list. Only the first choice among the multiple entries is visible in the List under that field. Even if I edit the entries in the SharePoint list it is still not showing the multiple entries in that field. Is this a bug? or am I doing anything wrong? Anyone else facing this same issue?
Link an existing form with a new spreadsheet
Hi, my questions are quite simple really and are directed at Microsoft: When are you going to create the ability to link an existing form to a new spreadsheet? When are you going to make it possible to copy questions/menu options between forms? The bare functionality of MS Forms is embarassing. Regards, NoelCreate an Internal Support Ticket Hub with Microsoft Lists, Forms & Power Automate
Setting Up the Support Ticket Portal First, we will set up the support ticket portal. This is where ticket requests will populate, be triaged, assigned and managed. It's a central location where the support team members can keep track of their tasks as well as keep the client informed through automated notifications upon status changes. Let's get started! 1. Create the Microsoft List: Navigate to Microsoft Lists from the Microsoft365.com App launcher in the upper left. Select the “+ New list” and choose the “Issue Tracker" template. Fill out the list information (name, description*, color*, icon*, and associate it with a team or save to your lists) and select create to make your form (*optional). In this case, associating the list with a team is required as it is needed for notification purposes later on in the tutorial. Review the list items from the template and customize the list to what your organization needs. Include columns that capture essential details such as issue description, priority level, assigned to, and status. Ensure the list is set up to store all necessary information for managing support tickets. There will be items you need captured from the person submitting the form as well as items to triage, assign, and track the status of the case. 2. Creating the Support Ticket Form In the list menu, select the "Forms" tab to create a new form. Customize the form by removing or unchecking questions that are designed for the support team, leaving only the questions needed from the person submitting the ticket. For example, you’d remove the Priority, Status and Assigned To fields from the form because those items are not determined by the submitter, but by the internal staff triaging the case. Ensure the form captures essential details such as the issue description, associated files, and contact information. 3. Enabling Notifications and Assigning Tickets In the form settings, select the toggle next to "Notify me" so that whenever a new item (support ticket) is submitted, you are immediately notified. This ensures that you don't miss an urgent request. Preview your form Check for changes or adjustments you’d like to make. If everything is good, congratulations! You’ve made your support ticket form! 4. The Workflow Process: Now that your form and list are created you can test out your new form and ticket portal. Grab the link to your new form by selecting the forms button again in the menu. Select the link sign to copy the link. Let's test things out. Fill out the form with information as if you are an employee submitting a ticket about an issue. Refresh and check your Microsoft List to make sure the form responses were automatically added. Triage the case. In the Microsoft List, double click on the form submission list item. Here, the support admin will triage the case by assigning it to a member of the support team, updating the status of the ticket to "In Progress" and assigning it a priority status. When a ticket is assigned, the assigned staff member receives a notification, ensuring they are aware of their new task. If they need to get in contact with the employee that submitted the case, they are able to come to the list item, and check for contact/email details in the email column. Team members can update the status of the ticket to "In Progress" when they start working on it and then to "Completed" once the issue is resolved. These status updates help track the progress of each ticket and ensure timely resolution. Congratulations! You have an internal support ticket portal and form. To further enhance the transparency and efficiency of your internal support ticket system, you can implement additional notifications to keep the requester informed about the status of their ticket. By setting up automated notifications in Power Automate for when a ticket is marked as "In Progress" and "Completed," you ensure that the requester is always aware of the current status of their issue. This not only improves communication but also boosts confidence in the support process, as employees feel assured that their concerns are being actively addressed and resolved. 5. Automating Notifications with Power Automate Create a Flow: From the Microsoft365.com app launcher, open Power Automate. Click "+ Create" and select "Automated Cloud Flow". Choose a flow name and set the trigger to "When an item or file is modified". Configure the Flow: On the canvas, select the trigger to enter the required data. The site address your Microsoft List is attached to and the list or library name. Next, we must add a trigger condition in order for the flow to only trigger when the status column has been changed. In the settings tab add the following trigger condition NOt(equals(triggerOutputs()?['body/Status'], triggerOutputs()?['body/PreviousStatus'])) Return to the canvas to create a new action. Select the + sign under your trigger. In the search menu, search for the condition action. For the value of the condition, we want to choose the Status Value from the dynamic field (the lightning bolt). We want to make sure the condition states “Status Value is equal to In progress”. (Capitalization matters here so make sure the capitalization of “In progress” matches the way it is spelled on your Microsoft List”. In the "True" column of your condition we will add a new action. Select “Send an email (V2) Inside of your action select, “Switch to Advanced Mode” to be able to enter dynamic fields or fields directly associated with your form submission. In the "To" field, select the lightning bolt for a dynamic entry. And select the “Issue logged by Email”. This will add the email address of the form sender to the “To” field and who the notifications will be sent to. In the Subject field type and appropriate title such as “Support Ticket Status Update”. In the Body field type a message to the requester. For example, "Hello, you are receiving this message to notify you that your support ticket for" (dynamically insert the name of the issue) “has been changed to “In Progress”. At this point, the flow now sends notifications for when the status column has been modified to “In Progress. Now, let's do the same and send a notification for when the status has been changed to “Completed”. In the False column, we are going to add another condition. The values for the condition will be the same except where it once said, “In Progress” it will say “Completed”. You want the statement to read “Status value is equal to Completed”. In the true column add the same action for sending an email and fill out the details accordingly. Save and test your flow. Test and Deploy: Test the flow to ensure it works as expected. Select Test and choose Manually. This specific flow is triggered when the status column has been modified to “In Progress” or “Completed”. Test both separately to make sure both works. You will see green check marks and receive a notification to the email you provided earlier when filling out the form with sample data. In this example, I tested the flow by updating the status to “In Progress” so in this case I have green check marks along the left side because that follows the first conditions. The green check marks will follow the right-side path if I choose to test the “Completed” status. Here is a copy of the email that was sent to the inbox. Once satisfied, deploy the flow to automate the notification process, enhancing communication and satisfaction. Conclusion By leveraging Microsoft Lists and Forms, you can create a robust internal support ticket system that streamlines the process of submitting, triaging, and resolving support requests. The integration with Power Automate further enhances this system by automating notifications, ensuring that all parties are kept informed throughout the process. This setup not only improves efficiency but also boosts employee satisfaction by providing a transparent and responsive support system.Pre-fill Responses in Your Microsoft Forms
We are excited to share that Microsoft Forms now supports pre-filled links, making your data collection process more efficient and improving data accuracy. This feature not only allows you to set default answers for your questions, it empowers you to strategize how you would like the responses categorized. To help you better understand how to leverage this new feature, let's try it together with an online training feedback survey.
Branching to previous questions in Forms??Workaround??
Hello! Does Forms allow you to branch from one question to a previously used question? I need this to collect data from multiple sections instead of creating a new Form for each question. Example: Q1: Select Insurance Coverage * Auto (what kind of Auto) * Home * Flood Q2: What kind of Auto? ** New (Would you like add'l coverage) ** Used (Would you like add'l coverage) Q3: Would you like add'l coverage? ** Yes ( Q1) .........<<????>>> ** No (End) Answering YES - The user could then go back to select another coverage and fill out the appropriate questions. Doesn't seem to work. Thanks!!! Matt
Restrict date submission in forms
I've recently made a digital marketing email request form so my team can better manage the email requests we get from various parts of our organization. Ideally, we would like for requesters to only be able to choose an email send date that is at least a month away from the date they are submitting the form. Is there any way to restrict requesters from picking a date that is less than 4 weeks from the date of their form fill in Microsoft Forms? Branching off of that if my above question is possible - would it be possible to to add a "Rush Request" field requiring justification/reason that appears if a requester does choose an email send date that is less than 4 weeks from the date of their form fill?
