2
votes

I have an installation of Dynamics CRM 4.0 that consists of two environments: one for development and one for production. We have an entity (a custom one) that contains currency-related attributes (currency and exchange rate) in the production environment, but the same entity in development does not have those same attributes.

We attempted to sync these entities up by exporting the customizations for that entity from production and applying them to development, but those two currency-related attributes do not appear in the exported schema data (customizations.xml).

Is there something about the currency lookup and the exchange rate attribute that prevent them from being exported?


Update and more details:

The CRM installation has been updated to the latest rollup (21) with no effect.

The attributes make sense in the context of the entity (it represents a country), but to my knowledge, these two fields are not being used. The entity was added to our system as part of a vendor customization. We are simply trying to keep our development environment synced with production, and we are stumped as to why these two fields will not export.

The entity has no money attributes.

1
Is there anything to be discovered by exporting all customizations?klugerama
Does the entity contain money fields?ccellar
@klugerama: No. After exporting all customizations, the XML definition for the entity in question still does not contain the exchangerate or transactioncurrencyid attributes.Matt Peterson
@ccellar: No, no money fields.Matt Peterson

1 Answers

1
votes

Do these attributes show up when you explore the metadata on the production system, i.e. by using the list.aspx. In other words: have these two attributes been added to the system in a supported way?