Hi Steve,
That should not be a limitation on the Consume REST API feature. All attributes/inputs/outputs inside REST API's have a "Original Name" property that allows dashes.
If you are trying to Expose a REST API, yes it is a current limitation that will be lifted on the next major version of the Platform.
Currently you have an easy workaround, just add a OnRequest callback and do a
![]()
![]()
Note: also regarding the ardojson, you don't need it for this. But just for the record, there are versions of the component in the forge that are compatible with any platform version 7.0+.
Edit: just noticed that when i wrote this initially had incorrectly OnResponse instead of the OnRequest. Fixed the text, but my screenshots are still wrong. It's the same thing but just on the other callback and the replace the other way around "smtp_id" -> "smtp-id"
Regards,
João Rosado
That should not be a limitation on the Consume REST API feature. All attributes/inputs/outputs inside REST API's have a "Original Name" property that allows dashes.
If you are trying to Expose a REST API, yes it is a current limitation that will be lifted on the next major version of the Platform.
Currently you have an easy workaround, just add a OnRequest callback and do a
Replace(CustomizedRequest.RequestText,"""smtp_id""","""smtp-id""")and then call your attribute smtp_id
Note: also regarding the ardojson, you don't need it for this. But just for the record, there are versions of the component in the forge that are compatible with any platform version 7.0+.
Edit: just noticed that when i wrote this initially had incorrectly OnResponse instead of the OnRequest. Fixed the text, but my screenshots are still wrong. It's the same thing but just on the other callback and the replace the other way around "smtp_id" -> "smtp-id"
Regards,
João Rosado