You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launch Fiori generator and choose a data source that is not Local CAP Project
On Project Attributes step, provide as Project folder path an app folder that is part of sample CAP Java project
Expected results
User is prevented from continuing with the following message: The selected project folder is part of an existing CAP project. This application must therefore use the local CAP project as the data source
Actual results
User is prevented from continuing with the following message: The project folder path already contains an SAP Fiori application in the folder: c:\SAPDevelop\New\cloud-cap-samples-java-main\app. Please choose a different folder and try again.
Screenshots
Version/Components/Environment
Add any other context about the problem here
OS:
Mac OS
Windows
Other
Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered:
Related Feature
#2427
Description
When non-CAP Fiori app is generated into a CAP project folder with pre-existing Fiori apps, incorrect error message is shown.
Steps to Reproduce
app
folder that is part of sample CAP Java projectExpected results
User is prevented from continuing with the following message:
The selected project folder is part of an existing CAP project. This application must therefore use the local CAP project as the data source
Actual results
User is prevented from continuing with the following message:
The project folder path already contains an SAP Fiori application in the folder: c:\SAPDevelop\New\cloud-cap-samples-java-main\app. Please choose a different folder and try again.
Screenshots
Version/Components/Environment
Add any other context about the problem here
OS:
Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered: