flexipage | a flexible jQuery plugin for paginate content | Frontend Framework library

I doubt it's sharing related (so not the org-wide settings). If it was sharing it'd simply always return 0 results but no big red errors.

If you remove the line with does the error go away? If it stays - it's problem with permissions around the custom code or Case_Type_Data__c). If it goes away - it's something with creating ERT_Case_Type__c)

Check the Profile (or Permission Sets if you use them) rights to:

• Read the source object (Case_Type_Data__c) and all referenced fields (Level_1__c...)
• Create the target object (ERT_Case_Type__c) and read/edit all referenced fields (Level1__c... but also Case__c)
• Read on the Case object and Case.CaseNumber, Case.Subject fields
• Permission to execute the Apex class (renamed to Stack, right?). And maybe add permission to run LookupSearchResult too.

I suspect you have enabled some critical updates (Setup -> Critical updates or Setup -> Release Updates) like "Restrict Access to @AuraEnabled Apex Methods for Authenticated Users Based on User Profile" or "Require Permission to View Record Names in Lookup Fields"

You're asking for a lot, we wouldn't have your custom object. And this is old code, ui:inputSelect is deprecated for 1 year now. I'll try to help a bit but the whole thing needs your work too. And examples we can reproduce easily.

I'm going to cheat and use Philippe Ozil's ready component for the lookup/autocomplete thing. It means you'd have to save LookupSearchResult class, the whole aura component and 2 aura events in your org before reading below. That's some prep work but it's battle-tested :)

Apex class

Could you use

JavaScript is case-sensitive. 2nd Console should be lowercase, I suspect it throws an error about undefined object.

You can use your browsers JS console (in Chrome Ctrl+Shift+J) to inspect such errors. It also helps to go to Setup -> Debug Mode and add your user in there. SF will get bit slower but you'll see more human-readable code and errors instead of optimised, minified mess.

If it still throws errors - use console to check what error exactly and edit your question?

P.S. change it in callback handler too

So the proper way to handle this would be by using the aura:html component. There are a few parameters you would set for this:

1. aura:id- String- your id to locate the elements within JS
2. tag- String- the html tag
3. HTMLAttributes- Map- No need to set this explicitly on the .cmp, we'll use Js

Like other base Lightning components, including , does not support the Task or Event objects.

The list of supported objects is here, in the Lightning Aura Components Developer Guide. The underlying limitation appears to come from the UI API, which doesn't support Task and Event.

After further looking at your code I see you are not actually calling your apex controller.

You need to add $A.enqueueAction to your getString.

The angular compiler is not included at runtime in AOT compilation (default for Ionic production builds), it's not a good idea to not use AOT for ionic as you want the app to be as fast as possible.

You may use HTML Agility Pack and RegEx on the attribute value: