Skip to main content
Solved

Dispatch Console resource in EAM

  • October 13, 2025
  • 6 replies
  • 62 views

Forum|alt.badge.img+1

Hello

I have an EAM project. I need to know if the dispatch console can work with Services.

I can see the work tasks in the console, but I can't see the resources.

What configuration should I have to achieve this?

I can configure the configuration in FSM, but I can't access the resources in EAM.

 

 

Best answer by Nethmini Kosvinna

Hi ​@Miguel Alejos ,

You will see resources in DC once you run Generate Schedules and Capacity for resources from resource detail page. You can run it either for a resource structure or for a resource group or for an individual resource.
Make sure to refresh DC window as well.

Thanks,
Nethmini

6 replies

kasunhp
Sidekick (Partner)
Forum|alt.badge.img+9
  • Sidekick (Partner)
  • October 13, 2025

Hi,

 

Did you create scheduling datasets and connect them?


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • October 13, 2025

Hello, thank you.

Yes, I've generated the connection, the dataset, and the resource connected to the dataset.

I'll send the views.

Regards.

 

 

 

 

 


Nethmini Kosvinna
Superhero (Partner)
Forum|alt.badge.img+18

Hi ​@Miguel Alejos ,

You will see resources in DC once you run Generate Schedules and Capacity for resources from resource detail page. You can run it either for a resource structure or for a resource group or for an individual resource.
Make sure to refresh DC window as well.

Thanks,
Nethmini


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • October 14, 2025
I think it's a problem with my environment, I have another environment that works by doing the same steps.

Nethmini Kosvinna
Superhero (Partner)
Forum|alt.badge.img+18

Hi ​@Miguel Alejos , 

May be the issue here is with the Employee record. As the HR schedule is used employee should have a valid HR schedule defined under employee file.

Thanks,

Nethmini


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • October 16, 2025

The problem was the type of time in the calendar, it was solved, thanks to everyone.