Prerequisites
- [x ] Have you tested the operation in the API directly?
- [ x] Do you have the latest SDK version?
- [ x] Review the compatibility matrix before opening an issue.
Describe the bug
In configutation_templates module, there are some parameters that either takes no effects or makes no sense at client side. Those are :
createTime
lastUpdateTime
latestVersionTime
validationErrors
template_version
As those parameters will be determined after Template creation, user should not input them.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

When provide createTime, lastUpdateTime and lasterVersionTime with hypothetical values during Template Creation.
Although the backend accepted those values and return 202
But while validation using dna/intent/api/v1/template-programmer/template/${templateId}

Those parameters did not take any effects at all (which is expected since these values are generated by the backend, not to be defined by users)
Environment (please complete the following information):
- Cisco DNA Center Version and patch: Version 2.3.7.5-70431
- Python version: Python3.8
- SDK version: dnacentersdk 2.6.10
- OS Version:
Additional context
I suppose this is the problem with DNAC API itself, should contact API team for further discussions.
Prerequisites
Describe the bug
In
configutation_templatesmodule, there are some parameters that either takes no effects or makes no sense at client side. Those are :createTimelastUpdateTimelatestVersionTimevalidationErrorstemplate_versionAs those parameters will be determined after Template creation, user should not input them.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

When provide
createTime,lastUpdateTimeandlasterVersionTimewith hypothetical values during Template Creation.Although the backend accepted those values and return 202
But while validation using

dna/intent/api/v1/template-programmer/template/${templateId}Those parameters did not take any effects at all (which is expected since these values are generated by the backend, not to be defined by users)
Environment (please complete the following information):
Additional context
I suppose this is the problem with DNAC API itself, should contact API team for further discussions.