This content has been marked as final. Show 2 replies
You did not mention what version of the product you are using.
In recent versions, if you Expired and then Unexpired immediately afterwards, there should be no difference in the resource. What you are describing would seem to indicate you have multiple "versions" of the resource in the library. Each version has a new effective date. The version of DAL resource that will be loaded is determined by the date of the run and not necessarily the transaction date.
To verify, go into Library manager and filter for your DAL resource name. Change the filters to show ALL versions and ALL revisions. Be sure to press the button to Filter Now.
Within each version - like 0001 - make sure that all the revisions have the same effective date. Technically you are not supposed to be able to set a revision to a different date within the same version - except for the expiration revision. So, if the unexpire did not change the effective date back to the same date as the other revisions, that would be a problem.
But if you see that you have more than one version listed - as well as revisions in those versions - then note the effective dates for those. The runtime is going to pick up the one that is effective based upon the date that you did each run.
Thanks for the information. I am using Documaker 12.1.
I do have only one version with multiple revisions. I was maintaining the same effective date 1/1/1980 for all revisions.
When I expired a resource the Version is 1 Revision 153. I expired a resource at this point and unexpired the same then it became Version 1 and Revision 154. After that what ever the changes I have done after Version 1 and Revision 154,it is not reflecting in GenData processing.