Known Issue Knowledge

Known Issues

Defects:

  • When performing Batch Denials, the date picker in Internet Explorer requires a user to double click.
  • Group headers show in print packets even if none of the questions are visible to the person printing it.
    • For example, if a group on an application form contains exclusively admin only(or internal) questions and an applicant prints the packet, the applicant will see the group header in the packet, though none of the questions or answers will show up.
    • This only happens on print packets, not when the admin is viewing the form.
    • This can also happen to reviewers if a group is exclusively admin only questions.
  • Users are unable to change the formatting of instructions in print packets even with the use of custom print packets.
  • A user's organization cannot be removed, if you choose no organization in the dropdown and save the user will still have the same organization.
  • The "Added" column on the users search page is showing a date based on UTC time not a foundations local timezone setting.
    • This is scheduled to be fixed in the next major release.
  • If an admin uses the view duplicates link in the warning box while reviewing a form to see duplicate organizations based on taxid and tries to merge the organizations, the organizations are archived instead.
    • This is scheduled to be fixed in the next major release.
  • When sending emails one at a time that use the same attachment if the email service hasnt finished sending the attachment on the first email, subsequent emails will throw an error and not be sent.
  • The select all options are not enabled when configuring reporting pre-filters.
  • When adding a user to an organization using the Add Contact button on the organization summary page the button for copying the organization address to the contact profile is grayed out.

Usability:

  • During registration a message shows on the organization page that tells users they cannot edit their organization information even if this feature has been enabled.
    • The content can be updated to match which fields are allowed by contacting support@foundant.com
  • When making merge templates please add quotation marks around any value that may contain parenthesis or other special characters.
    • For example: if you are using { MERGEFIELD Answer } make sure to put it in the document as "{ MERGEFIELD Answer }"
    • Text that main contain parenthesis are things like:
      • organization description
      • comments
      • answers
      • any other field that accepts parenthesis or other special characters
  • During the review process, questions marked as "Admin Only" in form builder are not considered when calculating if an evaluation is finished (which is what gives the reviewer the green checkmark).
    • This means that in order for a user to get a green checkmark, all non-required "Internal" questions must be answered if all the required questions on an evaluation are "Admin Only".
  • When a GuideStar search is performed through GLM, GuideStar uses a different way of searching that may return fewer results.
    • For example, if you search for "Friends of Stoughton Center", in GLM, no results will be returned. In GuideStar, however, you will get a result for an organization named "FRIENDS OF THE STOUGHTON AREA YOUTH CENTER INC".
    • In other words, searches through GLM must contain a subset of the organization's name according to GuideStar.
    • If you know the organization's tax id, this is a more accurate way to search through GLM because it should return the same results as searching for the same tax id on GuideStar's site.
      • The only exception to this is if the organization has chosen to "opt-out". In this case, they will show up in a GuideStar search if you have an account with them but it will not show up in GLM even when searching by Tax Id.
  • The Form Modified dates are all 3/6 and 3/7 for follow up forms.
    • We noticed this on release and the explanation is that the forms were all modified as part of the 5.0 release because we added questions that used to be report fields to there.
  • If a user is filling out a form and they choose to use a browsers auto-fill option, the auto-filled answers will not automatically save.
    • The fields will still be saved when the user clicks save as draft or submit, the only time they will not be saved is if the user leaves the page after the auto-fill without having first clicked save or submit.
    • This happens most commonly on fields that are often auto-filled, like First Name, Last Name, Address, Zip Code, etc.
  • Administrators do not need to click the Edit Icon for admin only and internal questions that are not read only in order to make changes to them. These autosave.
    • This is in the release notes but was brought up again as feedback. If a user finds this counter intuitive, one possible option is they can mark the question as read only. That way it will appear as all the other questions do and will require the edit icon to be clicked.
    • Product team discussed this and the green highlight was supposed to help with this assurance.
    • It would also be helpful if Admin Only questions are placed together in a "for internal use only" question group. They could even add instructions for themselves or other administrators to explain this.
  • File Upload Fields do not show "Save and Cancel" instead, the Edit button is disabled until a file is uploaded. This is because once a file is chosen it is uploaded. You don't have to "save" this change, it saves automatically.
    • This is noted in the release note, but came up again as feedback.
  • Before 5.0, all Approved requests (not yet Closed) could be accessed by clicking the "Granted" link off of the dashboard. In addition to requests that were just approved, the list of "Granted" requests also included those with a status of Follow Up Draft, Follow Up Submitted, and Follow Up Complete. With 5.0, the "Approved" requests do not include those Follow Up statuses. To access approved requests that are have Follow Ups assigned, submitted, or complete, you have to click the Follow Up Draft / Submitted / Complete links from the dashboard.
  • The Applicant/Administrator role combination that many Administrators use to test what their applicants see is no longer a reliable resource for this type of testing. There are many options that show to Administrators that do not show for applicants so it makes this type of view invalid. The best practice recommendation is for an Administrator to create a test applicant (or evaluator) account if they wish to see what an applicant (or evaluator) will see.
  • While empty nested lists can still be created, the handling has been improved. Users viewing the form with the empty nested list will see the label and/or instructions but are not required to answer it if the field is required.
  • Nested lists cannot have applicant-facing comments attached to them.
  • When building merge templates or custom print packets, a user can no longer refer to a field using the "RF_Field_Name" syntax (for example, "RF_Grant_Number"). The field must be referred to using its field code. The field code can be found by generating a merge template for a specific process.
  • If an Administrator or Grants Manager has the ability to edit responses and they are viewing an evaluator's form while it is in Evaluations Open, they will have full edit capabilities without clicking the pencil icon. As noted in the section "Administrators and Grants Managers can edit any users' answers", this is because they have the ability to answer "Admin Only" or "Internal" questions (and questions on evaluations are "Internal Only")
  • The nested list container and all categories of the nested list show up when generating a merge document as possible fields to merge. However, they show up out of order. This is due to the fact that they have the same sequence.
    • For example, say you have a nested list called "Name of School" and it has categories like "State", "City", and "School." Then you can grab the merge tag to "Name of School" which will match the way production handles these. Specifically, it will merge all the answers separated by the separator character "&&&&&&&&&>." Or you can grab just "City" (for example), and it will only merge the answer to the "City" drop down list question within the nested list. As mentioned though, they will show up in the list in a random order … perhaps, "State", "Name of School", "School", and then "City."
  • Quick exports from the workload pages ("Application Submitted", etc.) and the Search Requests and Decisions page will not include any form questions by default (even if they were previously report fields). To include these, a user will need to update the appropriate quick export data set.

Reporting:

  • When a data set name is changed, the changed name is not reflected in any saved reports that had been using it.
    • For example, if a saved report uses a data set named, "2014 Approvals" then the data set is updated and renamed "2015 Approvals" the saved reports will still have "2014 Approvals" for the name of the data set they use.
  • If formulas are being used in reporting make sure to set the data type of the column to be the correct expected value otherwise issues can arise. For example, if a field uses two numbers in a formula but returns text after the logic the field needs to be set up as a text field.
  • We upgraded our reporting solution (Logi Analytics). This upgrade has introduced some differences in how formulas are calculated:
    • If you expect a field you are using as part of a formula column to contain blank values, you will have to make a copy of that column. Then, using an "IIF" statement, you will need to change any blank values to a value Logi can use for calculations.
      • For example, say you have columns A, B, and C, and you want C to equal A + B. If either A or B could have unanswered values, you will need to make new columns based on A and B. These new columns would be A2(new) – which says if A is blank put 0, otherwise put the value from column A – and B2(new) which says, if B is blank put 0 otherwise put the value from column B. Then column C should be A2(new) + B2(new).
      • One of the biggest challenges with this is that Logi will work as you might expect for the first 100 blank values it encounters. But after 100 errors, it will stop processing the calculation and the rest of the values will be calculated incorrectly, which can give the impression that Logi is working even if it is not.
  • If you are trying to group and aggregate, the sub-group will account for all items within itself but the total count of all groups will exclude blank cells for the field on which you are aggregating. For example, in the screenshot below, you will see the count of values for the one request is reporting 5 but the total count of all values is 2, which does not make sense.

  • During the 5.0 conversion, report field templates were removed. Therefore, any report field that was referencing a report field template will now show up with its own name in reporting instead of the report field template name.
    • For example, if a foundation had two processes using the "Geographic Area" report field template and in one process called it "County" and another called it "School District", both County and School District will have the same reporting field code after 5.0. But in the reporting tool, you will not be able to find a question called "Geographic Area". You will see a question for "County" and one for "School District." Note, though, that in 5.0 reporting, you will be able to combine these into a single field for a report.
      • One way you can find these while rebuilding reports is by going to production and generating a mail merge template for the "Shared fields only." This will give you a list of report field templates and their field codes. The field code from production is the same as the field code after the 5.0 upgrade. Therefore, you can take this field code and search in the 5.0 reporting tool for all the fields that use this field code. This will be especially helpful when rebuilding reports in order to track down fields that may be used in filtering, grouping, or formulas. The screenshots below should help demonstrate what to do. Even though they use project name, the concept is the same.

Was this article helpful?