MEGATHREAD Target myDevices

All stores are different with what the aisles are labeled. For example, my store's market is in 'A' , however my old store's market was in 'G'
 
How quickly did this happen? Was it very rapid fire were the sounds were actually coming before the other sound finished, or was there some time in between them? I had only seen this on one of our earlier test versions, but we put filtering in to stop that (the sled will literally tell the iPod it is connected/disconnected about 20 times before it settles down, my only thought is maybe that one sled does it slower/longer than other sleds and we need to increase the filter)

It wasn't that rapid honestly. It would take a few seconds to connect to the sled as normal, then dieconnect, wait a few, reconnect, etc.

It would settle down after doing that a few times until it went to sleep, then started up again
 
All stores are different with what the aisles are labeled. For example, my store's market is in 'A' , however my old store's market was in 'G'
W is for grocery aisles in a super. Most pfresh remodels and new pfresh stores moved market to G to run along one of the side walls.
 
It wasn't that rapid honestly. It would take a few seconds to connect to the sled as normal, then dieconnect, wait a few, reconnect, etc.

It would settle down after doing that a few times until it went to sleep, then started up again

Thanks, that makes sense, if you get the same device again and it is still acting up let me know, we might need to extend the length of the filter if there are devices out there that take that long to make up their mind on if they are connected or disconnect.
 
My mydevice has worked perfectly several days in a row. o_O Wait for it...
I feel like I'm having more issues, getting logged out more, etc. And I use the same mydevice five days a week so I'm used to it's quirks...nothing I can reproduce or that's always happens. Just more buggy.
 
I feel like I'm having more issues, getting logged out more, etc. And I use the same mydevice five days a week so I'm used to it's quirks...nothing I can reproduce or that's always happens. Just more buggy.
I constantly get the 'cannot process your request. Ticket number is: 56797425785535 in myWork & REDwire. Always have close the app out and start again. @OtherGuy
 
Yup and they don't have the heft of the old pistols, can't really slug em into a box. Lol. Would retrieve the photo but no time.
 
I constantly get the 'cannot process your request. Ticket number is: 56797425785535 in myWork & REDwire. Always have close the app out and start again. @OtherGuy
I get that, or I'll scan something just fine, go to scan something else right after and no scanning suddenly. Normally I'd reseat it on the sled, but hubby hasn't found me the right screwdriver yet...
 
I constantly get the 'cannot process your request. Ticket number is: 56797425785535 in myWork & REDwire. Always have close the app out and start again. @OtherGuy
Same here. Using the scanner & stops. Also this happens, when you type letters to search something on the app, wait 20 seconds, finally comes up, answer the question. Then you lose the scanner to help another guestright after that.
 
We got the mobile mysupport update today and I'm really digging some of the changes.. Especially the ability to click POG numbers when you search for an aisle. Also, the additional info for specific POGs is great! The little touch of adding a 'discontinued date' to pogs is freaking wonderful too! It looks like capacity changes weren't added for this release but I did submit product issue tickets.

I don't know if it was a common issue but fir the first half of my shift, I was unable to make multi-item signs. The option did reappear sometime after lunch.
 
Man. I'd kill for some sort of ability to batch signs, or a specific mode for it. We're ripping up all the label strips in toys and replacing them with flex labels because of all the PTM we've flexed in. The needing to scan an item and wait for it to load before telling it to print labels is a real drag compared to the Label app on the PDAs...
 
@OtherGuy

Having some issues with price change. On some days (about 5 times in past 2 months), scanning a clearance item won't clear it off the system. This goes for sales floor and backroom. For example, when it shows 32 items in the backroom, I scan everything and it still shows 32 counts. I'm like okay, I'll just activate it all on the myDevice. Nope, this 32 counts. But it works on the PDA just fine. Can you look into this?

Also, battery life when doing price change sucks bad. I have to ask other tm's to switch with me once it hits 20% at least twice a day.
 
@OtherGuy

Having some issues with price change. On some days (about 5 times in past 2 months), scanning a clearance item won't clear it off the system. This goes for sales floor and backroom. For example, when it shows 32 items in the backroom, I scan everything and it still shows 32 counts. I'm like okay, I'll just activate it all on the myDevice. Nope, this 32 counts. But it works on the PDA just fine. Can you look into this?

Also, battery life when doing price change sucks bad. I have to ask other tm's to switch with me once it hits 20% at least twice a day.

We are seeing Rig items not clear either.
 
It looks like capacity changes weren't added for this release but I did submit product issue tickets.
It's in pilot, about 50 stores are going to get it in about a week.

@OtherGuy

Having some issues with price change. On some days (about 5 times in past 2 months), scanning a clearance item won't clear it off the system. This goes for sales floor and backroom. For example, when it shows 32 items in the backroom, I scan everything and it still shows 32 counts. I'm like okay, I'll just activate it all on the myDevice. Nope, this 32 counts. But it works on the PDA just fine. Can you look into this?

Also, battery life when doing price change sucks bad. I have to ask other tm's to switch with me once it hits 20% at least twice a day.
The number of defects that have been fixed for price change between sprint 28 and 32 is staggering, let me know if you still see the issue when your store gets 32. Just make sure that you aren't trying to do tomorrows work while in today's work load or vice versa.

As for battery we are looking at a few different things, but make sure you aren't running your brightness on full blast as that is the biggest drainer of battery power.


We are seeing Rig items not clear either.
There are two scenarios for this: If the Rigs task was created and then someone untied the POG and tied say a revision POG over it the task no longer maps to a location that exists. There isn't much we can do about having a task for a location that doesn't exist.
The other is some store tie Rigs tasks create issues, we have since fixed it, but it won't be out until version 35.
 
Back
Top