EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB46493: "Some input placeholders have not been mapped to any input objects. Map all placeholders before continuing." error message appears when saving the Freeform SQL definition for a transaction report.


Community Admin

• Strategy


"Some input placeholders have not been mapped to any input objects. Map all placeholders before continuing." error message appears when saving the Freeform SQL definition for a transaction report.

SYMPTOM:
 
After writing the SQL for a transaction services report, a user may encounter the following error after clicking OK to save the Freeform SQL definition:
 

ka04W000000uGEeQAM_0EM440000002CQA.jpeg

 
Sample Code/Error
Some input placeholders have not been mapped to any input objects. Map all placeholders before continuing.
 
STEPS TO REPRODUCE:
 
The following steps below are used to reproduce this issue in the Strategy Tutorial project.

  • Create a transaction report with the Tutorial Data database instance.
  • Define the Freeform SQL report as shown below 
ka04W000000uGEeQAM_0EM440000002CQB.jpeg
  •  

    Sql

    Begin Transaction
    Insert Into LU_BRAND
    (BRAND_ID)
    VALUES
    (,#1)
    End Transaction

     

     
  • Insert a dummy output object 
ka04W000000uGEeQAM_0EM440000002CQE.jpeg
  • Click OK and the error message will appear.

CAUSE:
 
This occurs when the custom query contains a # and then a number sequentially. For Transactions, # are reserved characters for the input objects. When opening a transaction report in SQL view, each input object will be replaced by #0, #1, #2...
 
ACTION:
Contact Strategy Technical Support for an update on this issue. 
 
KB46493


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

December 30, 2018