This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 18%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETA%3C/text%3E%3C/svg%3E)
In Luis I have been importing Entity Lists using the Json format and hit a limit of 160. The entity list was 200 items of different health care treatments.
Is this a extendable? What are the implications of long Entity lists.
There are other projects with large entity lists that I have in the pipe line.
My current workaround is to divide the treatments into categories using a name space notation can you see anything wrong with this approach?
If yes what is the recommended best practice?
Thanks
Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 45%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi, given the model limits, the recommendation is to use the LUIS dispatch tool to combine multiple LUIS apps into a parent LUIS app. Hope this helps!
Thanks
This makes sense as the some of the user utterances have common phrases such as "describe it" so the current state is important and if the state can be set until the user changes the subject. For example they may be interested in an asset then switch the subject to the heating the former being an "AssetType" and the latter being a "System".
So I can now break my models down into specific "Building Elements Types"