We need binary fields (example: field RECURRENCEDATA  in BATCHJOB table) to be exposed through X++ in FnO so it can be used in Azure Synapse Link tables as it is currently a known limitation:

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data#known-limitations-and-changes-to-behavior

Sample of some business impacts:

• What is the business impact of the issue?

need to apply governance on the batch jobs that recur. We want them to be easily distinguishable from the batch jobs that are not recurring, so that they can be forced into a naming convention. Recurring type batch jobs also need to be set to be run as a service account with elevated privileges, and not by a normal user who may leave the organization in the future.

• What is the financial loss if the issue persists?

Inability to govern the recurring batch jobs may lead to them erroring out. “Dead” batch jobs that my company relies on will stop critical functions like periodic posting of invoices, periodic backing of data and many other activities that the company can simply not afford NOT running. The losses can potentially be the entire business, which is billions of dollars of revenue.