Creative SharePoint Calendar and Power Automate Solution

%3CLINGO-SUB%20id%3D%22lingo-sub-1768920%22%20slang%3D%22en-US%22%3ECreative%20SharePoint%20Calendar%20and%20Power%20Automate%20Solution%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768920%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Community%2C%20I%20have%20a%20unique%20calendar%20to%20track%20data%20on%20company%20vehicles%20that%20I%20need%20help%20with.%20I'll%20explain%20how%20we%20were%20doing%20it%20and%20how%20I%20would%20like%20it%20to%20change.%20This%20is%20going%20to%20be%20a%20detailed%20explanation%20so%20thank%20you%20for%20reading.%20Currently%20we%20track%20departure%20and%20return%20miles%20for%20each%20vehicle%20we%20issue%20out.%20We%20were%20doing%20all%20of%20this%20in%20On%20Prem%20using%20Infowise%20to%20do%20the%20logic%2C%20but%20we%20have%20migrated%20over%20to%20Online%20and%20now%20I%20want%20to%20restructure%20the%20logic%20with%20Power%20Automate.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20On%20Prem%2C%20we%20had%20a%20separate%20list%20that%20stored%20the%20vehicle%20names%20and%20that%20was%20linked%20to%20the%20calendar%20via%20an%20Infowise%20Master-Detail%20Lookup%20field.%20Then%20we%20had%20a%20separate%20list%20that%20would%20store%20the%20departure%20mileage%20of%20each%20vehicle.%20In%20the%20calendar%2C%20whenever%20someone%20would%20log%20the%20RETURN%20miles%2C%20an%20infowise%20action%20would%20run%20and%20that%20return%20miles%20number%20would%20be%20dropped%20into%20the%20DEPARTURE%20miles%20list%20for%20the%20correct%20vehicle.%20This%20was%20so%20that%20when%20a%20new%20reservation%20was%20made%20for%20that%20vehicle%2C%20the%20previous%20return%20miles%20would%20be%20the%20new%20departure%20miles.%20See%20attached%20picture%20to%20see%20the%20On%20Prem%20version%20of%20the%20calendar%20list.%3C%2FP%3E%3CP%3EEx%3A%20the%20white%20cargo%20van%20was%20issued%20out%20with%20departure%20miles%20at%201000%2C%20when%20it%20comes%20back%20it%20its%20return%20miles%20are%201050.%20This%201050%20gets%20put%20into%20the%20return%20miles%20list%20and%20conditional%20logic%20drops%20that%20number%20into%20the%20field%20for%20the%20white%20cargo%20van%20and%20not%20another%20vehicle.%20When%20the%20white%20cargo%20van%20is%20issued%20again%2C%20an%20infowise%20action%20runs%20and%20autopopulates%20the%20Departure%20miles%20field%20with%20the%201050%20number%20from%20the%20return%20miles%20list.%20And%20so%20on.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20that%20we%20are%20in%20SPO%2C%20we%20don't%20have%20Infowise%20and%20I%20want%20to%20restructure%20the%20logic%20with%20Power%20Automate.%20Is%20there%20a%20better%20way%20to%20accomplish%20this%20with%20Power%20Automate%20than%20how%20we%20did%20it%20with%20Infowise%20and%20storing%20values%20in%20other%20lists%3F%20I'm%20thinking%20we%20could%20make%20use%20of%20variables%20and%20storing%20the%20return%20miles%20into%20a%20variable%20and%20recalling%20that%20variable%20for%20the%20departure%20miles%20on%20a%20new%20reservation.%20But%20it%20would%20have%20to%20be%20conditional%20to%20make%20sure%20the%20vehicle%20name%20is%20the%20same%20and%20its%20not%20getting%20data%20from%20another%20vehicle.%20Just%20trying%20to%20make%20it%20to%20where%20we%20don't%20have%20so%20many%20extra%20lists%20to%20pull%20and%20store%20data%20in.%20There's%20got%20to%20be%20an%20efficient%20way%20to%20accomplish%20this%20with%20Power%20Automate.%20I%20just%20don't%20quite%20know%20where%20to%20start.%20Any%20ideas%3F%20Thanks%20for%20reading%20through!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1768920%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalendar%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConditional%20Logic%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EInfowise%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPower%20Automate%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Evariables%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Hey Community, I have a unique calendar to track data on company vehicles that I need help with. I'll explain how we were doing it and how I would like it to change. This is going to be a detailed explanation so thank you for reading. Currently we track departure and return miles for each vehicle we issue out. We were doing all of this in On Prem using Infowise to do the logic, but we have migrated over to Online and now I want to restructure the logic with Power Automate. 

 

In On Prem, we had a separate list that stored the vehicle names and that was linked to the calendar via an Infowise Master-Detail Lookup field. Then we had a separate list that would store the departure mileage of each vehicle. In the calendar, whenever someone would log the RETURN miles, an infowise action would run and that return miles number would be dropped into the DEPARTURE miles list for the correct vehicle. This was so that when a new reservation was made for that vehicle, the previous return miles would be the new departure miles. See attached picture to see the On Prem version of the calendar list.

Ex: the white cargo van was issued out with departure miles at 1000, when it comes back it its return miles are 1050. This 1050 gets put into the return miles list and conditional logic drops that number into the field for the white cargo van and not another vehicle. When the white cargo van is issued again, an infowise action runs and autopopulates the Departure miles field with the 1050 number from the return miles list. And so on. 

 

Now that we are in SPO, we don't have Infowise and I want to restructure the logic with Power Automate. Is there a better way to accomplish this with Power Automate than how we did it with Infowise and storing values in other lists? I'm thinking we could make use of variables and storing the return miles into a variable and recalling that variable for the departure miles on a new reservation. But it would have to be conditional to make sure the vehicle name is the same and its not getting data from another vehicle. Just trying to make it to where we don't have so many extra lists to pull and store data in. There's got to be an efficient way to accomplish this with Power Automate. I just don't quite know where to start. Any ideas? Thanks for reading through!

0 Replies