bobbyu99

The `customType` is present in the model introspection schema. So this could be a bug or a feature for UI. @AnilMaktala  

Hi @djom202, It seems like you pushed some changes, then you see the following error. After rolling back those changes, the following error still persist, is that correct? If so,...

This error seems to come from part of the validation for `@belongsTo @hasMany @hasOne` directives. I don't see any field that uses these directives from the schema you provided. Just...

I am working to repro this issue, could you share with us which CLI version you were using when your schema was deployed successfully 30 days ago?

I noticed that `Vehicle` uses `plate` (a `String`) as its primary key, not `id`. `Geofence` references `Vehicle` through `geofenceVehicleId`, which is of type `ID!`. The types (`String` vs. `ID`) don't...

Sorry I am not sure I am following. Are you asking if it's possible to enforce uniqueness on a field like `plate` without making it the primary key?

Unfortunately, we do not have any directive that enforces uniqueness at this moment.

Reopen this issue and mark it as a FR and also duplicate for enforcing uniqueness on non-primary key field. Existing FR for Unique Constraints: https://github.com/aws-amplify/amplify-category-api/issues/286

@kouz75 How often does this issue occur/not occur? How many tables does your schema have? Is it possible to share your schema? It could be helpful for reproducing this issue.