Summary
Agreement-level fields such as Effective Date, Term Expiration Date, and License Number can be pulled from FranConnect using a custom Info Manager view, filterable by store lifecycle stage (Active, In Development, Archived, Terminated). Exported row counts may exceed the actual location count — this is expected behavior when a location has multiple records in the Owner(s) field.
How to Build the Report
- Go to Info Manager and create (or request) a custom view that includes the needed agreement fields: Effective Date, Term Expiration Date, License Number (and any other relevant columns).
- To filter by lifecycle stage, add a filter on store lifecycle stage to the view/report.
- Click the filter and toggle between stages as needed: Active, In Development, Archived, Terminated.
- Download/export the report once the desired filters are applied.
Note: If you need multiple stages included (e.g., all four), apply/select each stage in the filter before exporting, or run separate exports per stage and combine them.
Why Exported Row Count May Not Match Location Count
It’s expected for the exported file’s row count to be higher than the actual number of locations. This happens because the Owner(s) field can contain multiple owner records per location — when a location has more than one owner on file, it appears on multiple rows in the export, one per owner record.
Example from a real case: A view showed 13,149 locations, but the exported file contained 18,170 rows — the difference being locations with multiple owners each generating an extra row. This is confirmed, expected export behavior.
Takeaway: When reconciling an export’s row count against an expected location count, check whether the discrepancy matches locations with multiple owner records before assuming a data error.