Hi,

I think you can create a simple screen in the module it can be blank. Set it as the default entry screen. This will make the platform’s requirement for an entry point without affecting your core logic. Hope it helps.

Thanks,

Sriyamini J

When do you get this error ? Is is during debug? You should not be getting this error in the consumer application/module. 

This is not an issue for normal operations.

If this module is a part of an application with the UI module also which is the consumer you may need to define the UI module/ consumer as the default module for the app that will fix this issue.

Hi @Nathaly Virginia , I suspected that some developer perform debugging some logic in BL module, but forget to set Entry module for the debuger, this may cause the browser open a page with path to BL module in the browser, cause the log.
Or, just someone trying to put the path of BL module in the URL. So most of the time, this error can be ignored.

@Nathaly Virginia :It's normal to see this kind of error message when someone tries to access your module via https://platformurl/modulename. Only modules like Reactive, Blank, or Service can be accessed this way. Since your module doesn't have a default entry point, you can safely ignore this message.

Hi @Nathaly Virginia,

This issue occurs when there is no entry module set for debugging. The BL module should have a UI module that consumes it. You can set the entry point of the UI module for this BL module. 

Additionally, it’s not possible to directly access the BL module, so this error can be disregarded.