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

Cause and Classification are special fields #4

Open
JoePlant opened this issue Oct 10, 2013 · 1 comment
Open

Cause and Classification are special fields #4

JoePlant opened this issue Oct 10, 2013 · 1 comment

Comments

@JoePlant
Copy link
Member

One of the problems with the the Downtime Cause and Classification fields is that they are either ids or the names.

When reading data the Cause and Classification fields will return Cause and Classification as int when ResolveIdentifiers = false and will return the fields as string when ResolveIdentifiers = true.

When reading data in the GetData request the Cause and Classification will read either string or int depending on the ResolveIdentifiers property.

When writing data in the SubmitData the Cause and Classification will need to be int.

This makes it difficult to map the Ampla records to and from the <TModel> object, especially if there are Cause and Classification properties.

JoePlant pushed a commit that referenced this issue Oct 10, 2013
ResolveIdentifiers will determine whether the Cause or Classification is
expecting an int or string.
@JoePlant
Copy link
Member Author

If the Cause and Classification properties on the model are integers then then Repository will request ResolveIdentifiers = false for the GetData.

If the Cause and Classifications values are integers then they can be saved via the Add() or Update() methods.

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

No branches or pull requests

1 participant