Skip to main content
Question

FSM Report multiple Task_Id through string field

  • September 10, 2024
  • 8 replies
  • 51 views

Forum|alt.badge.img+5

I developed this report on Visual Studio 2017 with FSM extension.

The idea was to give to user some possibilities to generate the report.

It is working fine as the picture below. 


After setting up the Report admin registry for this report. 
I getting this error for the same filter:

 The task_id field is setup like:
 

What should I do to fix this issue ?

8 replies

Forum|alt.badge.img+10
  • Hero (Employee)
  • September 10, 2024

Hi @RTTATOVAR ,

I believe you need to change the operator from contains to equal. As an example the baseline task report you would use equal 245|264  to get both tasks.

 

Regards,

Morris


Forum|alt.badge.img+5
  • Author
  • Do Gooder (Customer)
  • September 10, 2024

Same problem.
I don't think it is a SQL exception because Visual Studio was able to export a report. I don't get it.

 


Shneor Cheshin
Superhero (Employee)
Forum|alt.badge.img+28
  • Superhero (Employee)
  • September 10, 2024

@RTTATOVAR 

I believe you need to set the taskid as numeric (int), and not varchar

Cheers!


Forum|alt.badge.img+5
  • Author
  • Do Gooder (Customer)
  • September 11, 2024

The purpose of doing this is to apply a similar filtering as we can do through the web client. It allows the user to combine multiple task_ids into the report.


If filled with only one task_id, it works, but that's not the intention.


Shneor Cheshin
Superhero (Employee)
Forum|alt.badge.img+28
  • Superhero (Employee)
  • September 11, 2024

@RTTATOVAR 

Thanks for the clarifications.

Do you have space characters in the parameters? Looks like from the screenshot.

Cheers!


Forum|alt.badge.img+5
  • Author
  • Do Gooder (Customer)
  • September 11, 2024

Thank you @Shneor Cheshin for your fast reply.
Even without space.

 


Shneor Cheshin
Superhero (Employee)
Forum|alt.badge.img+28
  • Superhero (Employee)
  • September 11, 2024

@RTTATOVAR 

I am out of ideas. The only thought is a product bug or compatibility issue.

What version of FSM do you run?

According to R&D VS 2019 is the preferred version for developing a report

Reports Support with FSM | IFS Community

Cheers!


Forum|alt.badge.img+6
  • Hero (Partner)
  • September 12, 2024

@RTTATOVAR in your query in RDLC, 

rather than declaring it as a variable using ‘SET’

can you try to use it directly in the where query. Also use the ‘equal’ as the operator

Something like below

 

where task.task_id ##TaskID $$TaskId OR @TaskId is null