Skip to main content

 Hi,
there is BUG with generated StateIndicator. Maybe is problem too long name. Entity name is not generated properly and only few first character is used so it make problem in future code generation.

Error occurs only when is StateIndicator used in page.

 

Entity name
Entity states​​​​​

 

-Base.client generated StateIndicator for nonexist entity “CCsFin”


 

Error in generation of code

Workaround exists:
Create new StateIndicator
or

Override StateIndicator and use proper Entity:

 

Looking for a close to issue. Expecting a reply.
 


@InfFilipV  which target version are u using? 22r1? 


@InfFilipV  which target version are u using? 22r1? 

Hi, @hamalk,
yes, 22R1.

 

 


I already renamed entity to shorten name and now it works good. So problem is definitely in length of Entity name (but still in limit and without warning).

BR
​​​​​​​Filip


Hi @InfFilipV 

 

Did a quick check, seems like having the keyword “State” with in the Entity name “ CCsFinStatementGen” itself is the issue. So the code generator breaks the name using the keyword State.

 

Seems like a bug in the code generator when having “State” keyword in the entity name while having a state transition with in the same entity model. 

 

Since we have a viable workaround we will fix this issue in 22R2-EA. via https://ifsdev.atlassian.net/browse/DXDEV-2548

Thanks a lot for reporting this for us.

 

BR
Harshini


Hi @InfFilipV 

 

Did a quick check, seems like having the keyword “State” with in the Entity name “ CCsFinStatementGen” itself is the issue. So the code generator breaks the name using the keyword State.

 

Seems like a bug in the code generator when having “State” keyword in the entity name while having a state transition with in the same entity model. 

 

Since we have a viable workaround we will fix this issue in 22R2-EA. via https://ifsdev.atlassian.net/browse/DXDEV-2548

Thanks a lot for reporting this for us.

 

BR
Harshini

Hi @hamalk ,
it could be, because I renamed it to CCsFinStmntGen and now it is OK.
Thanks you very much.
BR
Filip


Reply