Resolution 1
Our developers have researched this issue and the SQL Server agent it seems that there is no fix required here, there is xml stored in our Foglight topology which is not presented in the dashboard but all the details from the xml are.
Often there is no SQL text available in these circumstances, such as when a .NET SqlClient Data Provider runs an EXEC command which the Deadlocks panel would not be able to collect the SQL text from.
Users could try accessing SQL PI and reviewing the SQL Statements that were collected from the corresponding time range based on the Client Application column (Programs in SQL PI), login name column (Users in SQL PI), database, host name (Client Machines in SQL PI), etc.
Type "Deadlock" in the Search box in SQL PI to see the list of deadlocks there.

Additional deadlock information containing the SQL Handle might be also available by reviewing the following topology location for on-premise Foglight systems (non Foglight Cloud).
- Navigate to Configuration | Data
- Expand Management Server
- Expand All Data
- Expand DBSS_Data_Model
- Expand SQL-Server Data Model
- Expand Clusters
- Expand AGENT NAME
- Expand Instances
- Expand AGENT NAME
- Expand Deadlock Data
- Expand Deadlock Data Obs
- Expand History
- Click History
- Change the time in the top right corner to when this Deadlock occurred
- Click Deadlock Data to reset the data, new values should open up below
- Expand History
- Continue expanding the levels, until you reach the lowest level, such as SQL Server Deadlock Process, SQL Server Deadlock Process Frame, or Resource Waiter and then click that item (the details if there are any available) to show the SQL handle involved.
Resolution 2
There were rows that were part of the deadlocks but didn't have the SQL Text because they share the same SPID which already had the SQL Text displayed.