Here’s one of the clever commands to quickly search for entities
|
1 |
Get-D365ODataPublicEntity -EntityNameContains <Name> |
You can use it to find various entities. As always, PowerShell can pipe the results into other cmdlet’s:
Now, what data is in the result of one of these?
|
1 |
Get-D365ODataPublicEntity -EntityName <Name> |
The results include:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
Name : CustomerV3 EntitySetName : CustomersV3 LabelId : @AccountsReceivable:CustCustomerV3EntityLabel IsReadOnly : False ConfigurationEnabled : True Properties : {@{Name=dataAreaId; TypeName=Edm.String; DataType=String; LabelId=@SYS13342; IsKey=True; Is Mandatory=False; ConfigurationEnabled=True; AllowEdit=True; AllowEditOnCreate=True; IsDimen sion=False; DimensionRelation=; IsDynamicDimension=False; DimensionLegalEntityProperty=; Di mensionTypeProperty=}, @{Name=CustomerAccount; TypeName=Edm.String; DataType=String; LabelI d=@SYS7149; IsKey=True; IsMandatory=False; ConfigurationEnabled=True; AllowEdit=True; Allow EditOnCreate=True; IsDimension=False; DimensionRelation=; IsDynamicDimension=False; Dimensi onLegalEntityProperty=; DimensionTypeProperty=}, @{Name=AddressBrazilianCNPJOrCPF; TypeName =Edm.String; DataType=String; LabelId=@GLS379; IsKey=False; IsMandatory=False; Configuratio nEnabled=True; AllowEdit=True; AllowEditOnCreate=True; IsDimension=False; DimensionRelation =; IsDynamicDimension=False; DimensionLegalEntityProperty=; DimensionTypeProperty=}, @{Name =PartyType; TypeName=Edm.String; DataType=String; LabelId=; IsKey=False; IsMandatory=False; ConfigurationEnabled=True; AllowEdit=True; AllowEditOnCreate=True; IsDimension=False; Dime nsionRelation=; IsDynamicDimension=False; DimensionLegalEntityProperty=; DimensionTypePrope rty=}...} NavigationProperties : {@{Name=RebateAndDeductionsAgreementHeaders; RelatedEntity=RebateAndDeductionAgreementHeade r; RelatedRelationName=CustomerV3; Cardinality=Multiple; Constraints=System.Object[]}, @{Na me=CustomerProductDescriptions; RelatedEntity=CustomerProductDescription; RelatedRelationNa me=Customer; Cardinality=Multiple; Constraints=System.Object[]}, @{Name=AssetMaintenanceWor kOrderParentProjectsV2; RelatedEntity=AssetMaintenanceWorkOrderParentProjectV2; RelatedRela tionName=CustomerV3; Cardinality=Multiple; Constraints=System.Object[]}, @{Name=ValueModelC ustomer; RelatedEntity=FixedAssetValueModel; RelatedRelationName=AssetValueModelCustomer; C ardinality=Multiple; Constraints=System.Object[]}...} PropertyGroups : {} Actions : {} |
I’ll do another post describing one of the newest additions to the module,
|
1 |
Invoke-D365ODataEntityAction |
But, for this we will need to look at a different entity, since CustomersV3 does not have any action (as you can see above)
Remember, you can find the powershell module here: https://github.com/d365collaborative/d365fo.integrations