Experience.FellowshipOne.com

Thanks for the reply. So I guess my 10000 foot question is this - with trying to maintain a best practice of keeping F1 as the database of record, what is the ''best practice'' recommendation/'suggestion for integrating things that are not available through DE or API such as Event Schedules, Building and Room info, Activities, etc....with web site ...

How do you deal with duplicates doing it this way? Once you dump it - when you did that again do you tell it to not duplicate based on something like phone or email? But what if that data changes for a person?

Thanks Nick - this wil be very helpful to forward on - especially coming from the ''horses mouth'' (no insult intended!). I am technical and do our development and we had some people who have heard ''discussions'' that I thought had been misinterpreted and as we looked at going to Google Mail/Apps we were actually looking for the ''pull'' ...

OK - there has been some confusion within our church on exactly what this API will and will not do - the non-technical staff and leaders think that this will be the end of needing ANY custom code to interface with F1 data. As an example an option was brought up to move from an in-house MS Exchange server solution to a hosted Google Mail option ...

We are curious how anyone else is interfacing Outlook with F1 membership info in terms of making the contact information available through Outlook? We have MS Exchange and our plan (in development now) is to build an interface to pull membership data into Exchange Global Address book, but we are also entertaining moving to GMAIL instead of ...

We are working on a good way to display complete event/activities information on the church web site that is being entered in F1. How is anyone else doing this? We want to display all related info about an event, including the building/room and the ministry linked to the event. I have not found a comprehensive report that shows all of ...

If anyone needs it I have the login integration done within asp.net (vb) - fairly simple to do using the dll's that FellowshipOne provides. I also have a VB subroutine that parses out the Individual XML file into it's components and makes it available as an object.

Same here - we would like to know if this is realtively close - otherwise we have to start figuring out how to extract the data through csv files, etc... and I'd rather not do that just to turn around and have this be available.

We are in the same boat - starting to build interfaces and it would be nice to know at least a BALLPARK timeline - obviously not holding you accountable to nay timeframe given - to know wether to hold of on a significant amount of development that would have to be redone. Can you tell us - is this next quarter? End of Year? This time next ...

In case anyone is interested in a .NET snippet, here is part of my class that verifies the login - F1 provides a DLL (DataExchange.Common.dll) as part of their example code set that you can register and use. It makes your coding fairly simple and readable, and object based. This is in VB, but easily translatable to C#. Hope this helps ...

I aksed the same thing when first starting with this and at this point there is not a test environment. However, I was told that you could use some naming conventions that support could go in on request and remove for you - such as names starting with zzz, etc... I personally think this is needed for new users and for testing ''what ifs''...

I don't see this, but not sure if I'm just not looking in the right place or if it is not there. I would like to enter descriptive information about an activity. We are looking to export our activities to the web site and currently we are keeing the text in a database outside of F1. Does this exist?

We are wanting to export activity data so that we can use it on our web site and display an events calendar. Is anyone else doing this? We would like to avoid duplicate entry of activities both in F1 and our web site if possible. I cannot find a report that displays all activities and the associated info (date, time, location, etc...) and I was ...