 Danny asks, as I have a flow that is supposed to create item in the SharePoint list with the results of the form. When the list item is created, it's empty. Anyone know why it's empty? I don't know why it's empty, but I can give you some things to look for. Without obviously looking at it myself, I can't tell you why. The first question is, is it empty, empty? Like it creates a completely empty row in SharePoint, or does it give it the title and then it's not filling in any of the other values, the other fields? In your Power Automate flow, look at the flow run and find the create item and click on it to expand it. It will show you the inputs and the outputs. If the outputs are all blank, then you have a dynamic value error. You're putting in the wrong values, or you're not putting the values at all. It's not magical. You do have to tell it what values to put into the SharePoint list. You also want to check before that, if the inputs are empty, or if the outputs are empty also, look before that at the values from the form. Every single Power Automate that I do that comes from a data source, the trigger is when it's new, when it's created, when it's modified, when it's whatever happens, I always add a get item right after that. Whether you're getting the SharePoint item or getting the forms data, always get the item. Make sure that has the data in it as well. Basically, follow the trail through and see if the data is getting corrupted or missing or deleted anywhere in the Power Automate. Those are your best bets. Other than that, there could be a problem, but I use create item all the time, so I know that the action itself works. I would check the flow run, expand the action, and see if the data is there. The other thing is the data that's coming from the form could be a drop-down list. If you don't have those exact same values in the destination SharePoint site and it can't map them, then you don't let it add its own values, it's going to put nothing. It could be like you're saying, you've got to make sure they're apples on apples when you are mapping, and then if you make changes to the form, you've got to make changes to the SharePoint list and vice versa. People forget that. Don't refresh. Sometimes those new things don't show up. You have to actually refresh the connection to the SharePoint list or the form to make sure that the changes are showing up so you can map them together. Yes. Can you tell I've done that? Right. When you map those values for choice fields, read the field name in the Power Automate action, read the field name very carefully, and make sure you use the dynamic value that matches. If you use the choice field as your dynamic value, it will try to put the entire field in to a one-value field instead of using the choice field value dynamic value. Yes. And the data types are also a big deal too. If you've got text on one side and it's a date on the other, vice versa, it's not going to be able to map the data type as well. I wonder if it's getting any errors. We can't create these because of the data type mismatch type. I can't remember the exact error, but it comes something like that saying you've got text over here and this is a date. I can't put the two together. Right. I would be curious to know if the action is showing the data. Basically, is the data disappearing before the create item action or is the data disappearing during the create item action? And then that would go back to what Sherry was just saying of maybe you're putting the wrong type of data into the field and so it's getting confused. There is my Microsoft Access Queen hat. Just put that on. Right. Can you tell?