Question: How can I bind a `Datagrid` with two columns (`DataGridTextColumn` and `DataGridComboBoxColumn`) to an `ObservableCollection<Team> Teams`?

The `DataGridTextColumn` is bound correctly. But nothing is displayed in `DataGridComboBoxColumn`.

***Code-behind***

```
   public class Team
   {
      public string Name { get; set; }
      public List<string> Members { get; set; }
   }

   public class ViewModel : INotifyPropertyChanged
   {
      public event PropertyChangedEventHandler PropertyChanged;

      private ObservableCollection<Team> teams = new ObservableCollection<Team>
      {
         new Team()
         {
            Name = "A", Members = new List<string> {"John", "Jack"},
         },
         new Team()
         {
            Name = "B", Members = new List<string> {"Sarah", "Anna"},
         }
      };
      public ObservableCollection<Team> Teams
      {
         get { return teams; }
         set
         {
            teams = value;
            RaisePropertyChanged("Teams");
         }
      }

      private void RaisePropertyChanged(string propertyName)
      {
         var handler = PropertyChanged;
         if (handler == null) return;

         handler(this, new PropertyChangedEventArgs(propertyName));
      }
   }

```

***XAML***

```
<DataGrid ItemsSource="{Binding Path=Teams}"
          AutoGenerateColumns="False">
    <DataGrid.Columns>

        <DataGridTextColumn Header="Team" 
                                    IsReadOnly="True"
                                    Width="*"
                                    Binding="{Binding Name}"/>

        <DataGridComboBoxColumn Header="Members" 
                                        Width="*"
                                        />

    </DataGrid.Columns>
</DataGrid>

```

Answer: 
AWS recently announced support for regional API endpoints using which you can achieve this.

Below is an AWS Blog which explains how to achieve this:

[Building a Multi-region Serverless Application with Amazon API Gateway and AWS Lambda](https://aws.amazon.com/blogs/compute/building-a-multi-region-serverless-application-with-amazon-api-gateway-and-aws-lambda/)

Excerpt from the blog:

> 
> The default API endpoint type in API Gateway is the edge-optimized API
>  endpoint, which enables clients to access an API through an Amazon
>  CloudFront distribution. This typically improves connection time for
>  geographically diverse clients. By default, a custom domain name is
>  globally unique and the edge-optimized API endpoint would invoke a
>  Lambda function in a single region in the case of Lambda integration.
>  You can’t use this type of endpoint with a Route 53 active-active
>  setup and fail-over.
> 
> 
> The new regional API endpoint in API Gateway moves the API endpoint
>  into the region and the custom domain name is unique per region. This
>  makes it possible to run a full copy of an API in each region and then
>  use Route 53 to use an active-active setup and failover.
> 
> 
>
Unfortunately, this is **not currently possible**. The primarily blocker here is CloudFront.
*MikeD@AWS* provides the info on their forums:

> 
> When you create a custom domain name it creates an associated CloudFront distribution for the domain name and CloudFront enforces global uniqueness on the domain name.
> 
> 
> If a CloudFront distribution with the domain name already exists, then the CreateCloudFrontDistribution will fail and API Gateway will return an error without saving the domain name or allowing you to define it's associated API(s).
> 
> 
> Thus, there is currently (Jun 29, 2016) no way to get API Gateway in multiple regions to handle the same domain name.
> 
> 
> 

AWS has no update on providing the needful since confirming existence of an open feature request on July 4, 2016. [AWS Form thread for updates](https://forums.aws.amazon.com/message.jspa?messageID=728350)