Hi Mary,

Thanks for the suggestion. This seems pretty straightforward and quite a bit less work on our side. I'll run this by our product team and see what other things we need to consider on this, but assuming I'm not overlooking anything, this is probably something we could work into a more near-term release. I'll try to keep you posted regarding the status.

Thanks,

-chris

posted September 22, 2013 by Chris Dahl, Foundant Technologies

Hi Mary,

Thanks for updating your request. I think implementing this idea would be useful for a lot of folks, but at this point, though, it's not a near-term priority. We'll keep it on the list and as we work through other more pressing items, look at moving it up.

Thanks,

-chris

posted April 29, 2013 by Chris Dahl, Foundant Technologies

Hi all,

Thanks for the suggestions. In regard to updating Contact Information, improving how Organizations and Contacts are managed is a major focus for us in 2012. We are currently in the process of defining the first cut of some of those changes, which involves making the distinction between the Executive Director’s contact information and the applicant’s contact information more obvious. As we work through the initial changes, we will definitely consider how to best prompt users to keep their contact information current.

In regard to notifying users that an existing Tax ID is already in the system ... over the last few months, we’ve actually discussed this a bit. One idea was to create a message that would display when a user was trying to create an organization with a duplicate Tax ID ... something along the lines of “An organization with this Tax ID already exists in the system. Please contact the administrator to avoid creating duplicate organizations.” Over time, this message would be customizeable but we’ve received feedback from other clients that they’d rather field a few inquiries upfront than deal with the cleanup after duplicates are created. At this point, I don’t think we would prevent the user from proceeding, as some organizations (i.e. regional chapters of a national organization like Ducks Unlimited) may actually share Tax IDs. Would this be something that might work for you?

You also might look at the Idea Lab item “Let Organizations Search by EIN Number” ... there are some comments there around ideas for helping prevent duplicate organizations as well.

-chris

posted June 22, 2012 by Chris Dahl, Foundant Technologies

Hi Jen & Katie,

Katie ... when you say "pull a report", I'm assuming you mean from Reports Beta - is that correct? You're definitely correct about the difficulty of using the Follow Up Submitted status to determine which follow up was submitted ... given the many uses of follow up reports, it is exceedingly challenging to come up with statuses to make it easier to determine which forms have been submitted and which are outstanding.

However, one thing we are working on a product specification for is an analysis grid (like Decisions, Pending Requests, etc.) that will be specifically for Follow Ups. Barring any unforeseen challenges, I'm guessing this should be in the product by April 2013. This should have more of the follow up information that people need.

Also, as part of the 3.2.0 release (currently in our DEMO environment), on the FollowUp Submitted and FollowUp Draft pages, we have replaced the process name with the form name. Hopefully that will also be helpful.

Jen ... after having to use Data Export a LOT lately to help a user with an issue, believe me, I'm all for the ability to save data export configurations. I'm not sure when we'll be able to roll that change out as there are other high-priority enhancements already slotted for the first few releases of 2013, but I'm in favor of moving this up the list :-)

And both of you - thanks again for the suggestions, and all my best for a healthy and happy 2013,

-chris

posted December 27, 2012 by Chris Dahl, Foundant Technologies

How about form names?

If I want to pull a report for all people who have submitted a grant agreement but have three follow ups, It's hard to distinguish from the follow up submitted status which follow up was submitted.

posted November 16, 2012 by Katie Kaufmann, MRAC

fingers crossed for at least save functionality sooner rather than later!

posted November 15, 2012 by Jen Bokoff, Laurie M Tisch Illumination Fund

Hi Jen,

Just following up to say this is still on the roadmap, but it's not been prioritized yet for any near-term releases. I'll keep people posted when it is slotted for a release.

Thanks,

-chris

posted November 7, 2012 by Chris Dahl, Foundant Technologies

This would absolutely do the trick for now. Saving would be super helpful. I'd look forward to that update!

One of the reasons I started with the big, unlikely ask is that we have had to merge different exports a few times - ie a payment export with an application export - to see all info together, and it would be amazing to be able to pull it all at once. But, since info comes from different forms, we can't do that in export data.

But, saving the export would be huge and make it a LOT easier. Thanks Chris!

posted September 27, 2012 by Jen Bokoff, Laurie M Tisch Illumination Fund

Hi Jen,

For the foreseeable future, we'll not be able to pull form fields into Reports Beta.

However, we do have a specification for adding the ability to save when doing Data Export. Given the current priorities, I'm not sure when we'll be tackling it, but I do know from using Data Export during development and testing that Save functionality there would be very useful.

Thanks,

-chris

posted September 27, 2012 by Chris Dahl, Foundant Technologies