Experience.FellowshipOne.com

is anyone else experiencing problems assigning a sub-status to an individual record in your database? We noticed this problem late last week. We can enter the edit mode, and assign the sub-status, but when the hit save the sub-status is not written to the record. The answer from support was to use a workaround by going through Add Household 2.0. They did say they were continuing to look into the issue, but I just wanted to see if anyone else had noticed this.

---

Rob Guilliams
Director of Computer Services
Highview Baptist Church
Louisville, KY

Hi Rob,

 Yes, we're having the same issue.  We've entered a support ticket and was given the same work around but it has problems too. 

 
We've also noticed that when we just change something (like DOB) on someone's record under the Basic tab and then hit Save - the sub status gets blown away.  Nice!!

So, no... you're not the only one! :(

 

Leeta Kennedy

Southeast Christian Church


 

---

Leeta Kennedy
Ministry Liaison Technician
Southeast Christian Church
Louisville, KY

Wonderful. Well at least we're not the only one's having these issues. I'm glad to see that someone still reads these forums every once in a while. It was beginning to seem like this was a dead forum like so many others I've visited. I posted a question over a month ago and never got a response from anyone, user or F1 staff.

---

Rob Guilliams
Director of Computer Services
Highview Baptist Church
Louisville, KY

Actually we asked that our staff not to immediately reply on the forums so as to give other users an opportunity to build the community.  Our staff is instructed to review unanswered posts from time to time but will typically only reply after a period of time has past without other users replying.

As to the bug that is mentioned here, it is a known bug. Issues like this are tracked and addressed within the F1 support tool. Admittedly we have a backlog of bugs to release. Many are fixed and going through the QA process. We were held up from releasing them while we upgraded to .NET 2.0.  We completed that effort last week so we should now be able to release these fixes soon.

Thank you for your active participation in the forums, it's very much appreciated.

Curtis Simmons
VP, Product & Services
Fellowship Tech
 

 

How long a period of time are the staff supposed to wait before replying? I posted a question on April 2 that has yet to be replied to by anyone except me. http://3cords.org/forums/thread/1375.aspx

---

Rob Guilliams
Director of Computer Services
Highview Baptist Church
Louisville, KY

Yes, we saw that forum post shortly after you posted it. However, as I said, we first we wanted to see if any users replied. Second, if you are experiencing a system issue, performance related, bug related, or anything else which you feel is not getting addresses adequately then we would love to dialogue about that directly with you over the phone. Our Director of Customer Services, Lance Dacy, would be a good first point of contact and then we can escalate from there. It's true we may not have answered every post but it is our directive of the Support and Delivery Services teams to check on it from time to time. Generally, the Support team works within the support tracking system. Forums can sometimes be very interactive, there are several great ones about Ford F-150s that I used to help me recently. But other times the user base may be unfamiliar with using forums and blogs. We believe that may be the case with the church user base but not entirely sure just yet. I know when we switched forum platforms over to 3cords we lost a bit of momentum. We had over 400 users registered on the old site and when we switched over users had to re-register. In hindsight that may have been a mistake as we've yet to match that number on the new location. Community involvment in the forums, blogs, and Regional User Groups, will be a big promotion item for us at our conference next week. And we'll be rolling out some new ways to share product ideas and consolidate access to the information over the next several months. Curtis S

csimmons:

As to the bug that is mentioned here, it is a known bug. Issues like this are tracked and addressed within the F1 support tool. Admittedly we have a backlog of bugs to release. Many are fixed and going through the QA process. We were held up from releasing them while we upgraded to .NET 2.0.  We completed that effort last week so we should now be able to release these fixes soon.

Curtis Simmons
VP, Product & Services
Fellowship Tech
 

 

Curtis, You mention above that the issue with sub-statuses being erased is a known bug. How long has this issue been known? Was it announced to the user community and I just missed it? It would be nice to know when bugs like this are found in the application. We just noticed it late last week, but now knowing that this issue was already recognized we are wondering how many people we might have lost sub-statuses on when we updated other information on their records. If bugs like this are occurring, and the workaround is not announced to the general user community, how can we be sure of our data integrity?

---

Rob Guilliams
Director of Computer Services
Highview Baptist Church
Louisville, KY

"If bugs like this are occurring, and the workaround is not announced to the general user community, how can we be sure of our data integrity?"

 

Rob, you are so right on this.  We are scrambling to figure out how many sub-statuses have been lost with this bug, and since we have huge database, this is quite a task.  Fellowship should have announced this bug on their homepage as soon as they knew of it's existence, especially since it affects all users!

 

Leeta Kennedy

Southeast Christian
 

---

Leeta Kennedy
Ministry Liaison Technician
Southeast Christian Church
Louisville, KY

I (we) concur with you and Leeta. Bugs that negatively affect data should certainly be given top priority and a client notification should likely be posted. It appears this bug was introduced into the Thursday, May 3rd release. Unfortunately, the ticket was not assigned the proper severity and therefore the process of routing to Development to fix it immediately was not followed. On a positive note the issue has been resolved and will be placed into production this afternoon. Furthermore, we are a learning organization and bringing an issue like this to light helps us to improve our manual and automated incident response processes. We're disappointed that any bugs make into production but I'm glad that the issues with our response to this particular incident was brought to light so that we might not only correct the bug but our processes as well.

Curtis S 

Curtis, Thanks for the update. I'm glad to know this should be fixed today. I must say however, that I am losing what faith I had in this product. This is not the first time we've noticed an issue that would bring the integrity of our data into question. Granted, this is the first time that data has actually been lost. On previous occasions it has been an issue of reports not pulling all of the pertinent data or pulling different data sets on successive runs. For example, several months ago our pastor wanted a directory of all members. I tested it on my machine and the resulting report was approximately 240 pages. I then watched the pastor's assistant run it twice on her machine with the same settings I had just used. The first pass resulted in a directory of approximately 190 pages and the second in a directory of more than 250 pages. Subsequent runs all netted the same 250+ pages so it might have been a momentary glitch, but it still brings the validity of data in reports into question. If we are to continue using F1 I need to know that the integrity of my data is secure and that when I run a report I am getting an accurate representation of the data which I requested.

---

Rob Guilliams
Director of Computer Services
Highview Baptist Church
Louisville, KY

Agreed. We have been internally discussing and planning a reporting solution for some time that would put the report creation into your hands. Well we now have an active data warehousing project that we can build a number of unique reporting solutions on top of. It is one of our top 3 initiatives. I'll post additional details as they become available.

Curtis S