Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attributes missing from select attributes #668

Closed
rappen opened this issue Mar 3, 2022 Discussed in #667 · 7 comments
Closed

Attributes missing from select attributes #668

rappen opened this issue Mar 3, 2022 Discussed in #667 · 7 comments
Assignees

Comments

@rappen
Copy link
Owner

rappen commented Mar 3, 2022

It is hard to find address attributes.
Can it be easier?

See the discussion.

Discussed in #667

Originally posted by ergobill March 3, 2022
Latest version of Xrm Toolbox (v1.2022.2.54) and FetchXML Builder (1.2022.3.1)

simple account entity fetch looking for Address 1 and Address 2 constituent fields.

None showing in the Select Attributes Window.
image

no errors that I can find.

@mtnmuncher
Copy link

Same issue exists for contacts
fxb_address_fields_not_available_from_select_attributes1

@rappen
Copy link
Owner Author

rappen commented Mar 4, 2022

Yes, because it is also stored in customaddress entity....
So we "know" how to see address attributes.
It would be nice to be easier...
Read the discussion to see how!

@mtnmuncher
Copy link

mtnmuncher commented Mar 4, 2022

My only comment would be that, the fetch xml, generated by advanced find, can no longer be used in FXB.

For example, this XML,

  1. advanced find, include all contact address fields.
  2. paste generated XML in FXB - see below.
  3. Additional fields are added by selecting 'select attributes. After clicking 'ok' all address fields disappear.
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
  <entity name="contact">
    <attribute name="fullname" />
    <attribute name="contactid" />
    <attribute name="address2_utcoffset" />
    <attribute name="address2_upszone" />
    <attribute name="address2_telephone3" />
    <attribute name="address2_telephone2" />
    <attribute name="address2_telephone1" />
    <attribute name="address2_shippingmethodcode" />
    <attribute name="address2_primarycontactname" />
    <attribute name="address2_postofficebox" />
    <attribute name="address2_name" />
    <attribute name="address2_longitude" />
    <attribute name="address2_latitude" />
    <attribute name="address2_freighttermscode" />
    <attribute name="address2_fax" />
    <attribute name="address2_composite" />
    <attribute name="address1_utcoffset" />
    <attribute name="address1_upszone" />
    <attribute name="address1_telephone3" />
    <attribute name="address1_telephone2" />
    <attribute name="address1_shippingmethodcode" />
    <attribute name="address1_primarycontactname" />
    <attribute name="address1_postofficebox" />
    <attribute name="address1_telephone1" />
    <attribute name="address1_name" />
    <attribute name="address1_longitude" />
    <attribute name="address1_latitude" />
    <attribute name="address1_freighttermscode" />
    <attribute name="address1_fax" />
    <order attribute="fullname" descending="false" />
  </entity>
</fetch>

After selecting 'select attributes.

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
  <entity name="contact">
    <attribute name="fullname" />
    <attribute name="contactid" />
    <order attribute="fullname" descending="false" />
  </entity>
</fetch>

Also, I don't think there is an effective way to return a flat model of address1 and address2, by using customeraddress entity.

@rappen
Copy link
Owner Author

rappen commented Mar 5, 2022

I see, I understand.
It does work pretty fine, if you have the right showing:
image

But I see we need it a bit better...
Working on it!

@rappen rappen self-assigned this Apr 6, 2022
@rappen rappen closed this as completed in 20fad5e Apr 15, 2022
@rappen
Copy link
Owner Author

rappen commented Apr 15, 2022

Selections:

image

Default: Checked (both)

@mtnmuncher
Copy link

mtnmuncher commented Apr 19, 2022

I 'pulled' your latest, and verified the new 'addresses' worked successfully. Cheers!

@rappen
Copy link
Owner Author

rappen commented Apr 19, 2022

Good to hear!
It will be released in about a week.
Stay tuned....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants