NW Scheduler/Publisher - Updates, Support, and Suggestions

[GoldenAge]

is it safe to upgrade to the latest version of some issues are still being worked out?

[Floyd]

Just now, GoldenAge said:

is it safe to upgrade to the latest version of some issues are still being worked out?

 

I have one major problem still? I don't know when it will be resolved.

[jwhess]

In my case the elders fixed all of the concerns in NWS so my NWP app works OK now.  The answer as to whether it is alright to update will depend on the main program being updated and adjusted to local needs.

 

I still get an error message about not everybody on my FSG having emergency contact info complete.  I understand there are a check box or two my Son-in-Law (cong sec) has to check to make it go away but it is not a problem.  he said he plans on a few minutes tomorrow to fix it.

[computerwiz]

3 hours ago, Floyd said:

 

Yes everything has been very stable since importing from KHS. I did that about 7 weeks ago. This problem with the EM contacts only occurred after the update Friday. I had no issues until after the update. And I don't even know how to "reset" it.

 

Whenever I send the EM contacts to the app its fine. It's only when receiving data from the app that it is a problem. So as of right now I don't feel safe importing EM contacts from the app. If I get any I will have to read the data in the preview and then manually update it.

 

 

Ok, I had some craziness with emergency contacts & importing a few weeks ago, but that was resolved for me.

 

I still don't fully trust importing data due to that. And so I always check what it was before importing, and what the import looks like, and then how it looks afterwards. The last few worked fine, but I don't get it often enough to say it's fully resolved.

 

One thing you could try doing is going to each emergency contact and adding "z" to the end of the name, and then going back and removing it. That would force an update + update the timestamp for each data object.  Learned that trick for congregation speaker issues.

 

Then once you do a data push to everyone, hopefully they'll all be on the same page and it will work right for you. 

[Floyd]

6 minutes ago, computerwiz said:

One thing you could try doing is going to each emergency contact and adding "z" to the end of the name, and then going back and removing it. That would force an update + update the timestamp for each data object.  Learned that trick for congregation speaker issues.

 

I have been doing that for my own EM contacts. But you are saying do that for all persons? For my own I have tried completely removing them and re-adding through the app. I have tried all kinds of combinations.

 

What I don't understand is that the preview says it's going to import it to my user id and then it imports to a random user id. 

[computerwiz]

19 hours ago, Floyd said:

But you are saying do that for all persons?

 

Yes.  It's worth a shot if you have the time.  And if it doesn't work, then you might need NWS support to chime in...

[Floyd]

2 hours ago, computerwiz said:

 

Yes.  It's worth a shot if you have the time.  And if it doesn't work, then you might need NWS support to chime in...

 

NWS support got back to me overnight and pushed out an update that seems to have fixed it.

 

 

[Cruzer]

 

I've messaged the NWS team regarding a few minor issues I've ran across with the latest release, but here are the ones we're still seeing with NWP. Anyone else seeing the same?

 

 

[Aja]

On 6/25/2023 at 7:50 PM, jwhess said:

I still get an error message about not everybody on my FSG having emergency contact info complete.

When I first updated I had to go back and reconnect everyone that had a "Linked to Congregation Record" designation, or in other words an emergency contact that is listed in the congregation person's of the program. They were all previously linked but the update caused me to have to relink them. 

[Cruzer]

11 hours ago, JoshD said:

 

I've messaged the NWS team regarding a few minor issues I've ran across with the latest release, but here are the ones we're still seeing with NWP. Anyone else seeing the same?

 

 

 

The latest build (#1286) resolved most of these for us 😁👍🏽. All of them appear to have been addressed for the exception of the "live" map view within a territory inside "open map".

 

[Aja]

I don't recall anyone mentioning it so I'll just throw it out there as a PSA. There is now a 4th "Gold" registration level that the new mapping features are locked behind. It's your call as to whether or not it's worth it for your congregation but just letting everyone know if you didn't already.

Edited June 27, 2023 by Aja
originally shared possibly sensitive info

[Broseph]

Yes mine shows the numbers for duties as well now, but didn't think of it as a problem. So it wasn't intentional?

[Cruzer]

46 minutes ago, JonE said:

Yes mine shows the numbers for duties as well now, but didn't think of it as a problem. So it wasn't intentional?

 

It wasn't a problem, just not necessary. The numbering before the duties has been removed however in the latest update 👍🏽.

[Jmystro]

During Silver registration, I tried to map out a territory and it worked for one territory.

 

For the next territory Scheduler kept crashing so figured I need Gold registration so I paid and upgraded.

 

Schedule is still crashing when I try to map/set territory boundary, anyone else experiencing this?

[molnarj]

In the new release this option is added:

 

• Added Assign Field Service 'Key Person' field. This is optionally used for Public Witnessing

What is Key Person referring to? Someone who has the key to the place where the Carts are stored? Or is it someone who has to be there, for instance a brother, when there is a more dangerous location? There can be as many as 7 keypersons  assigned to a certain location and time. ?? 

Any thoughts are welcome.

[Floyd]

I know with SMPW there is a "Key Man" who is responsible to getting the carts from the storage location and leading the group in the brief meeting for service. He has other responsibilities as well. He may oversee multiple locations. Perhaps NWS is trying to mimic that aspect.

[Jf800]

In the last update for NW publisher, the "add adress" button has dissappear for me. 

Edited June 29, 2023 by Jf800

[computerwiz]

1 minute ago, Jf800 said:

In the last update for NW publisher, the "add adress" button has dissappear for me. 

 

For the PC or the app?

[Jf800]

My mistake, in the last update for pc, the "allow send new adresses" was unticked.

[luisenriquereyes]

Problem I am having is after the updates to NW Scheduler, these settings get removed so you have to go back in to update them:
 

[Cruzer]

39 minutes ago, luisenriquereyes said:

Problem I am having is after the updates to NW Scheduler, these settings get removed so you have to go back in to update them:
 

 

Mine does the same, but it may be by design due to that it's personal information being displayed when enabled.

[Cruzer]

Is anyone's territory map view working? Our addresses are displayed correctly on the bottom half but the top half (map) has not worked since NWP 3.0 was released.

 

[orodriguez]

I adjusted the map boundaries in NWS by adding another point and the territory map is working in NWP. 

[Cruzer]

31 minutes ago, orodriguez said:

I adjusted the map boundaries in NWS by adding another point and the territory map is working in NWP. 

 

Perfect! Didn't think of doing that & they're now working for me as well 👍🏽

[dvdgarofalo]

Can someone drop a few screen shots of the NWP App for the territories features? We are debating whether to move from Territory Helper to NWS. I've done the map and data import. Need to clean up the data. But I don't want to implement it until I have more confidences in it. tia