Have you placed and tested the user parameters in the workspace, prior to the server app. Refer to the FME Academy Advanced course unit “Create Flexible Workspaces with Parameters 2024.1” https://academy.safe.com/path/fme-form-advanced/create-flexible-workspaces-with-parameters and/or the user parameters section https://support.safe.com/hc/en-us/articles/27200008210317-Parameters-Across-the-FME-Platform

Providing a sample fmw workspace, or better a fmwt template with the feature cache, as an attachment, would help others provide better advice here

Thanks so much ​@j.botterill.  Yes, I have been able to run the date filters applying the steps you mentioned but I haven’t been able to get results for attributes filtered within the selected date ranges.  I’ll have another review of the articles though - thanks for the tips!

Hi ​@andersonkma !

If the data isn’t filtering as expected after publishing the app, a few things to check:

• Make sure your date values are in proper FME datetime format. Use a DateTimeConverter if needed.

• For filtering, you can use a Tester, a SQL expression, or a WHERE clause directly in the reader if the source supports it (postgres will have all these options!)

• To work with date ranges, the DateTimeCalculator can help set up comparisons (e.g. start/end ranges). Also, check out FME’s datetime functions (like @DateTimeNow(), @DateTimeAdd(), etc) if you need dynamic dates. Our article DateTimes and FME goes into more details on how to work with datetime attributes. 

• If you’re not seeing results, try using a Logger or Tester to verify parameter values are actually matching what's in your data.

Let me know if that helps or if you want to share more details! 

Sanae

Thank you for the detailed explanation ​@sanaeatsafe!  I’ll give these options a try.  Stay tuned