1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Jump to navigation
Jump to search
m
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 12:27, 25 November 2015
, 12:27, 25 November 2015Added file naming convention.
m (Added info on field-re-use.) |
m (Added file naming convention.) |
||
| Line 93: | Line 93: | ||
=== Group reports in chronological order === | === Group reports in chronological order === | ||
Due to the way table segmentation works in OnDemand, you'll want to load the data in chronological order. When you name files, consider including a date field in YYYY-MM-DD format, so it can be sorted numerically at load time. This ensures that when the production server goes live, that end users will get speedy and fast database queries. | Due to the way table segmentation works in OnDemand, you'll want to load the data in chronological order. When you name files, consider including a date field in YYYY-MM-DD format, so it can be sorted numerically at load time. This ensures that when the production server goes live, that end users will get speedy and fast database queries. | ||
=== Name output files in AG.Date.App format === | |||
Write your report files with the following prefix: ApplicationGroup.DateFormat.Application | |||
This will allow you to load by Application Group, Date, and Application easily when you sort the files. By having the date as your second 'field' in the file name, you make loading in Chronological order easy and straightforward. | |||
=== Concatenate Reports === | === Concatenate Reports === | ||