Error when creating a PXDBLocalizeable field in a new table/DAC

What’s interesting is that UsrCityKvExt will be a table in your database and it should have nothing to do with your table.

You’ll have UsrCity and UsrCityKvExt

Do you see both tables in your database?

Thanks! This was my issue. I had created the table via database script so it did not create the KvExt table. Deleting my scripts and instead creating the table schemas from database then republishing the customization created these tables and solved the problem.

Follow-up issue now that I have the multi-language field working. When I create a PXSelector in another DAC that refers to this one, the SubstituteKey is not working (when I remove the SubstituteKey it will properly save the int value, but I’d want to display my CityName to the user in that users’ locale language). 

    #region CityID
    [PXDBInt]
    [PXUIField(DisplayName = "City")]
    [PXSelector(
      typeof(SearchFor<UsrCity.cityID>),
      typeof(UsrCity.cityID),
      typeof(UsrCity.cityName),
      SubstituteKey = typeof(UsrCity.cityName))]
    public virtual int? CityID { get; set; }
    public abstract class cityID : PX.Data.BQL.BqlInt.Field<cityID> { }
    #endregion 

this results in a selector pop-up that displays my cities without issue, but when a value is selected and I try to save the record I get this: 
 

I can’t find any documentation supporting what would need to be done to support a LocalizeableString in a PXSelector. Is it not possible to do this?

@kevlynch glad the KvExt part sorted it.

Not as the SubstituteKey, no. The popup works because it only reads rows. Saving is different. With SubstituteKey set, the selector turns the name you picked back into a CityID by selecting UsrCity where CityName equals that text. In that select, PXDBLocalizableString doesn't give the WHERE the plain name. It swaps the column for a subquery on UsrCityKvExt that returns all the translations joined together, which only get split apart after the row is read. "test" never equals that joined value, so the lookup comes back empty and you get the cannot be found error.

Stock PMCostCode shows the way around it. Its Description is a PXDBLocalizableString, CostCodeCD is the SubstituteKey, and Description is the DescriptionField. Do the same: add a plain PXDBString code column to UsrCity, make it the SubstituteKey, and set DescriptionField = typeof(UsrCity.cityName). The lookup then runs on the code, and the name shows as the description in the user's language.

I just tried this, and while I also no longer have an error message, what ends up being displayed in the field is the CityCD value, and not the CityName I’d want to see. Based on this, is the only way to get the CityName to display to add a calculated field that updates on change of the CityCD value?

 

Scratch that. I just found my solution by adding this to my PXSelector in the DAC entry. Thanks again for all your help.

SelectorMode = PXSelectorMode.DisplayModeText