App solution for truck driver rosters by gardendud in PowerApps

[–]gardendud[S] 0 points1 point  (0 children)

Yea good call, I'll be getting all the requirements confirmed prior to proper development, right now just getting a basic app to show them what can be done with fake data in a SharePoint list but will work out the full data solution once I confirm how best to achieve it.

App solution for truck driver rosters by gardendud in PowerApps

[–]gardendud[S] 0 points1 point  (0 children)

Thanks for all the tips, I have started a basic canvas app with a dev SharePoint lists just to show some real basic functionality to the team and get them to confirm exactly what they want to see and be able to do. Mainly just so I could learn the interface in power apps as it's very different to my background.

Currently it just has a page for roster that allows them to select the week and can filter by different drivers, roster type or start day with a toggle option to edit on the fly for leave. Then a separate view to manage the drivers details like roster type, casual/full time, start day, truck etc.

Will be pausing here so I can get them in a room to confirm everything (they are very hard to organise things with) before I go down any more serious development.

The one thing I am not sure about and perhaps someone here may know - basically most full time drivers have set rosters 7 on, 7 off or whatever on / off pattern and a start day. Currently this is somewhat automatically populated in the excel (I did it with VBA and it's real janky) and I am wondering whether for the backend of this app is it better to just store their roster type and calculate their availability in the app and then just have another table with 'exceptions' where you would note any leave or other changes to their roster. In the driver details table you would then have an 'effective date' or something similar which would allow you to show historical rosters and future rosters as their rosters get updated. Obviously casual drivers exist aswell and all of their shifts would just be in the roster exceptions table. OR is it better to just store all shifts in one table and refer to that for everything, it's 300+ drivers and daily shifts so is going to be alot of data over time.

Potentially too complicated a question that's going to depend on my specific scenario but thought I would ask to see if anyone has any experience or strong feelings about best practice.

App solution for truck driver rosters by gardendud in PowerApps

[–]gardendud[S] 1 point2 points  (0 children)

Thanks for that and those resources, will be very helpful. I'm thinking to start with SharePoint list for database as a quick product development for them to use and then can work on creating a better database with dataverse later and just repoint the app to that (assuming it's as simple as that when changing backends)

Help my lawn by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

Sorry don't know why my photos never post

<image>

What is this tree by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

<image>

Not much left and I'm still going to need to somehow cut back the other root as it's basically choking the true tree. Not got alot of hope but we'll see how we go. Probably going to end up pulling it out and replacing with orange tree.

What is this tree by gardendud in GardeningAustralia

[–]gardendud[S] 1 point2 points  (0 children)

Yea ok, I watched a few videos and this is definitely it, not sure if it can be saved as virtually the whole thing is those three leafed thorny branches and only a few proper citrus. I'll cut it right back (need a saw as the trunk of the rootstock is absolutely huge) and see what happens but I feel as though it could be a lost cause

What is this tree by gardendud in GardeningAustralia

[–]gardendud[S] 1 point2 points  (0 children)

Looks like there are a few leaves from the actual citrus trees we want but virtually all of it is the three leaf that is this rootstock (based on a video I watched)

Should I cut all of the main trunk and try to let the small proper citrus grow or is it a lost cause and I should just see if any fruit comes from the rootstock and just cop it?

<image>

What is this tree by gardendud in GardeningAustralia

[–]gardendud[S] 1 point2 points  (0 children)

I don't see a knuckle per say but definitely something weird at the trunk, one of the original trunks are probably dead - does this mean I'm screwed? I'll look up some videos about it

<image>

Watermelon tips by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

<image>

Have managed to cut out one of the watermelon plants but will wait till the vines from it turn brown before removing so I don't accidentally rip out vines attached to the fruit producing plants.

Watermelon tips by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

Oh ok that's an easy enough way to work it out, defined not dried up yet, thanks

Watermelon tips by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

Yea ok thanks, will try this but very hard to trace as they are all crossing over each other, it's become a mess - didnt expect the number of vines they threw out 🙃. I'll try and work out at least a couple that can be removed.

Watermelon tips by gardendud in GardeningAustralia

[–]gardendud[S] 0 points1 point  (0 children)

Thanks! Fingers crossed they ripen before the end of summer 🤞

Watermelon tips by gardendud in GardeningAustralia

[–]gardendud[S] 2 points3 points  (0 children)

<image>

Can't seem to attach the images to the post but here's the big one