beginCreateAndWait method is returning operation status instead of tracked resource (@azure/arm-workloads)

[hirenchalodiya1]

• Package Name: @azure/arm-workloads
• Package Version: 1.0.0-beta.1
• Operating system: Windows
• nodejs
  • version: 16.8.0

Describe the bug
While monitor creation beginCreateAndWait function has data type Monitor

const monitor = await client.monitors.beginCreateAndWait(
      resourceGroup,
      monitorName,
      createMonitorPayload as Monitor
    );

But response is long running operation and monitor properties are null

To Reproduce
Steps to reproduce the behavior:

1. Create any tracked resource using @azure/arm-workloads package

Expected behavior
Method should return Monitor object. So basically, id would be \subscriptions\<subscriptionId>\resourceGroups\<rgname>\providers\Microsoft.Workloads\monitors, name should be resource name not operation status name

Screenshots
Pasted above

Additional context
Add any other context about the problem here.

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Monitor:0.5532203,ARM:0.043992866,Network - Virtual Network:0.018207463'

[qiaozha]

@MaryGao Can you help follow up on this issue ? Thanks

[MaryGao]

Sure I am preparing the package for this fix.

[kazrael2119]

Hi @hirenchalodiya1 ，
I fixed this issue and regenerated this package. You can use this package to verify whether your problem is solved.
Here is the package:
azure-arm-workloads-1.0.0-beta.2.zip

[hirenchalodiya1]

@MaryGao @kazrael2119
New package resolves the issue.

[MaryGao]

Released here: https://www.npmjs.com/package/@azure/arm-workloads/v/1.0.0-beta.2

[qiaozha]

close it as resolved.