← 返回教程首页 | 视频图文笔记 第 13 / 14 期

Workday 报表全解:标准报表、自定义报表、数据源与字段(含租户实操)

Workday Standard Report in Workday HCM | ZaranTech

频道:Workday Learner Community(ZaranTech) 时长 01:33:28 发布于 2024-09-25 28 帧对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
标题只写了「Standard Report」,实际本集是一场 Workday 报表总课:前半约 55 分钟讲 Report Writer 内建、标准报表、报表类型、数据源、业务对象、Class Report Fields、字段类型、prompt、报表效率/上下文报表/安全;后半约 37 分钟进租户实操,先建 RM Salary by Org 报表跑出 18 行现薪/拟薪,再拆解一张客户报表 Compensation Change Report for Payroll -APAC 并搭第二张 Compensation changes for Region。字幕为 YouTube 自动生成,个别术语(如 class report field、optimize for performance)正文按正确写法订正,quote_en 保留字幕原样不改动;画面看不清处标注(待核对)。报表名、字段名、prompt 选项均照画面逐字记录。
1:15

Overview 架构总览

Overview 架构总览
  • Workday Report Writer 直接内建于 Workday,登录即可用,无独立入口/链接
  • 同一能力嵌入业务流程(business process / workflow),可从流程里运行报表或取数
  • 呈现方式:Dashboards、Scorecards、Embedded Analytics;大数据量走 Big Data Access reports
  • 可配 Excel template 实现 Automatic formatting,下载即排好版、省二次整理
  • 可作 Outbound Integration(Reporting-as-a-Service / REST)与 Mobile 访问;Workday Studio 的 Report Designer (BIRT) 定制 PDF/app 版式

"there is a Workday Report Writer. Uh but it's built into Workday, so when you log in to Workday, it's already part of the app and there's no separate um place to go to access Report Writer."— 有一个 Workday Report Writer,但它内建在 Workday 里,你登录 Workday 时它就已经是应用的一部分,没有单独的地方去访问 Report Writer。

2:45

搜索前缀与标准报表清单

搜索前缀与标准报表清单
  • 搜索前缀(非必需,可缩范围):rd: 只搜自定义报表;rd tag: 按标签搜自定义报表定义;field 按字段(含报表字段)搜
  • 举例:直接搜 head count 返回全部相关,rd: head count 只返回匹配的自定义报表
  • Workday 默认交付大量报表,Workday Standard Reports 报表用来查看它们,定位是「起点」,之后再复制改造
  • 右侧演示提示 Demo Standard Reports,按报表类别输入 worker
  • Security note:标准报表会列出全部报表(即使当前用户无权运行);运行它须属于 Custom Report Administration 安全域的组

"There's a report called Workday standard reports to view the Workday delivered reports. So, Workday by default gives you tons of reports and the purpose of that is to give you a starting point and then you can modify those later to customize it for your client or your customer."— 有一张叫 Workday Standard Reports 的报表,用来看 Workday 交付的报表。Workday 默认给了很多报表,目的是给你一个起点,之后你再改造成适合自己客户的定制版。

6:15

站点地图查看全部报表任务

站点地图查看全部报表任务
  • 另一种入口:点 profile 图标 → 站点地图(site map,需租户启用),列出该用户有权限的全部报表与任务
  • 滚动到 Report Writer 可浏览可访问的报表清单
  • 演示用 Worker Standard Report 时,Logan 用户默认无权运行——标准报表「可见」不等于「可跑」,仍受安全域限制
  • 从标准报表复制定制:报表上点 Actions(related actions)→ Standard Report 菜单里的 Copy → 复制后再 Customize 编辑

"There's other way to get to all of the reports, which is to click on the profile. And if you have site map enabled, not all tenants have the site map enabled, but um there is a site map icon, and then it will take you to the all the available reports and tasks."— 另一种拿到全部报表的方式是点 profile。如果启用了站点地图(并非所有租户都开),有个 site map 图标,点进去能看到可用的全部报表和任务。

7:45

标准报表类别与修改入口

标准报表类别与修改入口
  • 幻灯片标题 Modifying Reports,展示 STANDARD REPORT CATEGORIES(标准报表类别)截图
  • 复制标准报表后即进入编辑屏,先熟悉界面再上租户
  • 编辑屏左侧是 Columns,可增删列:加新列用顶部图标或每行右侧的 + 号,并支持重排(reorder)

"Once you're copied a report and you're on the edit screen um let's just familiarize with it before we go to the tenant. Um on the very left hand side uh there's columns you that you could add or remove."— 复制一张报表后就到了编辑屏,上租户之前先熟悉一下界面。最左边是能增删的列(Columns)。

9:30

创建自定义报表表单

创建自定义报表表单
  • 编辑屏可按业务对象(business object)选字段,并可覆盖字段显示名(overwrite the field's name)取更贴合业务的列名
  • 用 format masks 格式化输出;options 列控制如何展示数据
  • 选项示例 do not display if empty——某列无返回值时整列不显示
  • 自己建报表用任务 Create Custom Report;近一两年多了 Optimized for Performance 勾选,多数常用数据源并非性能优化型,需取消勾选才显示

"When we create your own report uh it's pretty straightforward task name. It's just create custom report. Uh one key thing is though in recent um year two years Workday has came up with an optimized for performance uh checkbox."— 自己建报表很直接,任务就叫 Create Custom Report。但近一两年 Workday 出了一个 Optimized for Performance 勾选项。

12:30

业务对象=Excel 工作表类比

业务对象=Excel 工作表类比
  • Workday 里数据存成业务对象(business objects),可类比成 Excel 的一张表或工作表,有行有列
  • 业务对象有 fields(字段)和 instances(实例);数据源提供对主业务对象(Primary Business Object, PBO)的视图 view
  • 图中链路:Class Report Fields → Report Data Source → Primary Business Object(Employee, All Active Employees view) → Related Business Object(Dependent)
  • 右侧示例:员工实例(Nathaniel Collins、Alice Owen、Cynthia Grossman 等,含 Job Title / Hire Date / Next Quarter)关联到 Dependent 的 Name / Age

"all of the data in Workday is um, they're stored as business objects. And think of those as Think of a business object as a table or a worksheet in Excel. Workday business object has fields and instances. And the report data source provides a view into the primary business object."— Workday 里所有数据都存成业务对象,把它想成 Excel 的一张表或工作表就行。业务对象有字段和实例,报表数据源提供进入主业务对象的视图。

18:30

报表术语定义表

报表术语定义表
  • Primary Business Object:报表的主对象,持有要展示的数据(1:1 或 1:N 关联到相关对象)
  • Related Business Object:与 PBO 关联的对象(如一名员工的多个受抚养人),PBO 上某字段把两者连起来,无需手工 join
  • Report Data Source:Workday 交付、承载业务对象的源,可理解为某 PBO 的视图 / 起始过滤;HR 侧常用约一打,高频只有四五个
  • Class Report Fields (CRF):按你的权限可见的可用字段,分三类——Workday 交付、计算字段、自定义字段

"class report fields, uh these are the available fields based on your security. These fields can be Workday delivered fields, calculated fields, or custom fields, and they're referred to as uh CRF, class report fields."— Class Report Fields 是按你的权限可使用的字段,可以是 Workday 交付字段、计算字段或自定义字段,简称 CRF。

25:00

常用数据源与主对象对照

常用数据源与主对象对照
  • All Active Employees*:仅在职员工,PBO = Employee;不含临时工、已离职、未来入职;过滤已内置,无需再加 filter
  • All Active and Terminated Workers:在职+已离职+临时工,不含未来入职;PBO = Worker
  • All Workers:系统内任意记录(在职、离职、未来入职),PBO = Worker
  • All Dependents:受抚养人数据,PBO = Employee Dependants
  • **Indexed Data Sources(Indexed Workers、Trended Workers)大数据更快,但见后文——不能加 prompt

"if you use all active terminated workers as the data source, this will have anybody who's currently active and who is terminated. And this will also have information on contingent workers, but it will not have future start date workers."— 如果用 All Active and Terminated Workers 作数据源,它会包含在职和已离职的人,也含临时工,但不含未来入职日期的 worker。

29:30

字段类型 CRF 图标速查

字段类型 CRF 图标速查
  • Text:简化文本;Rich Text:带超链接/可操作的文本(点员工名可跳到员工档案 profile)
  • 数值类 Numeric、Currency;时间类 Date、Time、Date and Time;Boolean(True/False) 字段旁显示 TF,勾=真不勾=假(如 Active status)
  • Single-instance:两对象 1:1(一名员工只有一个 pay group)
  • Multi-instance:两对象 1:N(如 worker 有多个 dependent)
  • Self-referencing instance:引用回自身,点进可看该对象详情与相关动作

"there is also rich text fields. And then when next to the field, you'll see these icons. rich text also has like hyperlink. That means you could take action or you could uh from that field, you could you could click on it and then you could get more information about it."— 还有富文本字段,字段旁边你会看到这些图标。富文本带超链接,意味着你可以对其执行操作、点进去看更多信息。

34:30

对象详情报表

对象详情报表
  • 报表名就叫 Business Object Details;运行时以业务对象为 prompt(如输入 Employee)
  • 返回该对象的:全部可用字段、相关业务对象、该对象所在的全部数据源、含该对象的全部报表——建报表前先跑它
  • 报表最多含四个标签页:Fields、Related Business Objects、Data Sources、Reports;某类下无数据则该标签隐藏
  • 用法:搜索栏输 business object,把对象名当 prompt 填入

"if you select employee or you put worker as the business object in this report, you'll get all of the fields that are available on that object, all of the related business objects, and all of the data sources uh this object is available on, and all of the reports uh which have this object."— 如果你选 employee 或在报表里把 worker 作为业务对象填进去,你会得到该对象上全部可用字段、全部相关业务对象、该对象所在的全部数据源,以及含该对象的全部报表。

38:30

对象详情四标签与关联计数

对象详情四标签与关联计数
  • 对象 Employee 的 Related Business Objects 标签:共 536 个相关对象(1 of 536 items),其中 Employee Compensation Event 链接数 = 14(高亮)
  • 右侧 Links from 显示 39 items(如 Adjustment For、BI Cosmos 12M CO…、Bank Statement Lir…,其余被截断,待核对)
  • 四个标签 Fields / Related Business Objects / Data Sources / Reports
  • 字段标签里如 Employee Compensation Event 有 1,189 个字段,多数字段用不到,需按主题过滤

"if you click on the fields tab, you'll see that in this case, the uh employee compensation event has 1,189 fields."— 如果你点 Fields 标签,会看到在这个例子里 Employee Compensation Event 有 1,189 个字段。

40:30

报表效率:选内置过滤的数据源

报表效率:选内置过滤的数据源
  • 数据量到 1 万、3–4 万行以上时报表性能才真正要紧,选数据源要兼顾仍返回全部所需数据
  • 优先选已带预置过滤(pre-built filters)的数据源,别在报表里自己加处理
  • 只要在职员工薪酬时不要用 All Active and Terminated,避免多带离职数据
  • Before / After Version 对比(All_Active_Employees → Worker Event - Completed):用带「事件已完成」的对象/数据源可省掉自建 filter

"choose a data source that already has the pre-built filters on it. So, you don't have to do that kind of processing within the report itself."— 选一个本身已带预置过滤条件的数据源,这样你就不用把这类处理放进报表里做。

44:00

上下文报表取数

上下文报表取数
  • 上下文报表:基于某个实例/事件直接取数,无需进 Report Writer;只要对象上有 related action 图标,其菜单里有 Reporting → Report Fields and Values
  • 演示针对某员工(Adam)的一次 marriage change(婚姻变更)事件,只返回与该事件相关、限于该人的薪酬数据
  • 也可从同一 related action 菜单选 Create Custom Report,直接跳到自定义报表界面继续选字段
  • 点 Report Fields and Values 会返回上千字段,需自行加合适过滤(如 Base Pay Current、Base Pay Proposed、Effective Date)

"It means reporting data based on the um the instance or based on a event, but instead of having to go to the report writer uh or to the report UI, just as long as there is a related action icon available, there is a menu called reporting, and from there, if you click on reporting fields and values, um you will get the data that's available for that action."— 它的意思是基于某个实例或某个事件来出报表,不用进 Report Writer 或报表界面;只要有 related action 图标,就有个 Reporting 菜单,点里面的 Report Fields and Values,就能拿到该动作/事件对应的数据。

47:30

报表类型全景

报表类型全景
  • Advanced(最常用):展示主+相关对象数据,可排序/过滤,输出为 spreadsheet;还可 enable as worklet、作 chart、作含小计/总计的财务报表
  • Composite:把多个报表合成一张,每个是 sub-report、可各用各的数据源
  • Matrix / Inbox:自定义分析分组汇总并下钻;X-Y 二维矩阵(四宫格/九宫格),常见于绩效/人才如 nine box
  • Search:按报表 filter 所选值展示搜索结果;facet = 报表 UI 里预置的过滤
  • Simple:面向新手、选项有限;Transposed:行列互换;Trending:随时间看汇总,dashboard 常用、可点入看明细

"these are all the different report types. So, the most common one um is called advanced and this allow you to display data from primary and related business objects. And you could sort, filter, and the data is shown in either a spreadsheet type."— 这些就是各种报表类型。最常见的是 Advanced,它能展示来自主业务对象和相关业务对象的数据,可以排序、过滤,数据以电子表格式展示。

53:00

Prompt 可从哪些地方取

Prompt 可从哪些地方取
  • Data Source:数据源自带 prompt(如 Employees by Organization 内置 Organization、Include Subordinate Organizations、Comparison Level)
  • Filter / Field:把用到的数据源过滤、字段作为运行期 prompt
  • Calculated Field:为报表建的计算字段也能当 prompt;Prompt Set 把多个 prompt 字段值成组
  • 效率建议:能用带内置 prompt 的数据源就用,别在通用数据源上手工造 filter/prompt

"when possible, use data source with built-in prompts rather than manually creating any filters and prompts on more a generic data source. So, just for efficiency purposes."— 只要可能,就优先用带内置 prompt 的数据源,而不是在更通用的数据源上手摇过滤器和 prompt,纯粹是为了效率。

54:00

报表安全与排障

报表安全与排障
  • 建自定义报表须属于以下允许安全组之一:Implementer、Manager、Report Writer、Setup Administrator、Temporary Report Writer
  • 报错 ISSUE: A USER CAN'T RUN A STANDARD REPORT,根因常是用户缺该报表所属安全域权限
  • 排障①:运行 View Security for Securable Item - Report,把报表名作为 securable item 填 prompt,得到该报表的 security domains 与 permitted groups
  • 排障②:运行 View Security Group for User 看该用户是否落在允许组里;不在就把用户加进有权的那个安全组

"in order to create custom report, your profile must be part of the one of these uh security groups. So, either it's part of the implementer, or manager, or report writer, or setup administrator, or temporary report writer."— 要建自定义报表,你的用户档必须属于这些安全组之一:Implementer、Manager、Report Writer、Setup Administrator 或 Temporary Report Writer。

55:30

实操建报表初始页

实操建报表初始页
  • 用例:某组织想知道成员构成、现薪 current salary、拟薪 proposed salary 及生效日期,并按组织来跑
  • Create Custom Report 表单:Report Name*、Report Type*(默认 Simple)、Temporary Report、Data Source
  • Optimized for Performance 勾选时只显示 Indexed 数据源,顶部红条 1 Error / View All 因必填未填
  • 按组织跑宜选已带组织过滤/prompt 的数据源(如 Employees by Organization),而非裸 Employee

"let's actually jump into the tenant and create a custom report. Create custom report. Okay, so let's think of a use case where um you are requested to for a given organization they want to know the composition of the employees in that organization. And they want to know what's their current salary and what is the proposed salary and the effective date."— 我们进租户建一张自定义报表。设想一个用例:某个组织想知道它员工的构成、现在的工资、拟议工资以及生效日期。

59:00

性能勾选挡住数据源

性能勾选挡住数据源
  • 报表明例名 RM Salary by Org(用姓名缩写便于查找),Report Type 选 Advanced;另有 Enable As Web Service、Temporary Report
  • 临时报表会标到期,需跑 delete temporary report 任务才清,方便试验不堆积
  • 输数据源 employee by org 时不出现——因 Optimized for Performance 预勾选,只显示 Indexed 数据源
  • 界面提示原文:Showing only Indexed Data Sources. You can unselect option "Optimized for Performance" to show all data sources.(取消勾选后才能选到 Employees by Organization)
  • Data Source 查找下拉分类:By Category / All / By Category and Primary Business Object / By Primary Business Object

"And it's because the optimize for performance checkbox is pre-checked. It says, "Right now, it will only show you indexed data sources and you can unselect for performance to show all data sources.""— 这是因为 Optimized for Performance 勾选框预先勾上了,界面写着:现在只显示 Indexed 数据源,取消勾选 Optimized for Performance 才能显示全部数据源。

1:01:00

列编辑器:主对象自动带出

列编辑器:主对象自动带出
  • 选完数据源 Employees by Organization 后,Primary Business Object 自动填为 Employee(Data Source Type = Standard)
  • Additional Info 下才有 Columns / Sort / Filter / Subfilter / Prompts / Output / Share / Advanced 各标签
  • Columns 首行放 Employee 业务对象、字段留空待选;可直接选主对象 Employee 上的字段,也能选隔一层(one degree)相关的字段
  • 顺手可加 Report Tags(关键词,供日后按标签检索报表),但需相应安全组权限

"now for that source, the primary business object is employee, and that's already populated over here. So, I could select any field that's available on that business object. And I could select any field that is one degree related to this business object."— 对这个数据源,主业务对象是 Employee,已经自动填好了。于是我能选这个业务对象上的任意字段,也能选与它只隔一层的字段。

1:04:00

搜 base pay 选当前基本工资

搜 base pay 选当前基本工资
  • 目标字段 Base Pay - Current(当前基本工资);先加 Employee、Employee ID 两个基础列
  • 在 Field 处搜 base pay 弹出 123 个候选,如 Base Pay as of Dec. 31st from Previous Year、Base Pay as of First of the Year、Base Pay Below Market Factor / Position 等
  • 名称过长/过复杂时可在 Column Heading Override 覆盖列头;作 web service 输出时更需覆盖
  • 提醒:选字段前先看字段 description,别误选候选人(candidate)的同名字段

"We need a salary data so I'm just going to type base pay and let's see what's out there. Okay. So there's a lot of fields related to base pay like base pay as of December 31st from previous year and so on. So the What I'm looking for is base pay current."— 我们需要工资数据,所以我直接输 base pay 看看有什么。出来一堆相关字段,像去年 12 月 31 日的 base pay 之类。我真正要找的是 base pay current。

1:07:00

换对象取加薪生效日

换对象取加薪生效日
  • Employee 主对象上的 effective date 都是员工相关的(如 Current effective date=求值时所用生效日),都不是本次加薪生效日
  • 要取「上一次基本工资上调的生效日期」,须换业务对象:用相关对象 Last Base Pay Increase
  • 已选列:Employee、Employee ID、Total Base Pay - Amount(Column Heading Override 改成 Base Pay)
  • 教训:起步简单,但发现取不到某字段值时,多半是业务对象选错,应去相关对象里找

"but if I want um the the effective date of the last pay last base pay increase I actually need to change the business object."— 但如果你要的是上一次基本工资上调(last base pay increase)的生效日期,就得改业务对象。

1:10:30

运行报表内置提示选组织

运行报表内置提示选组织
  • 点 OK 后有 Run / Test / Done 三选项;Test 只返回前 10 行,适合不确定过滤时快速验证、省加载时间
  • 这些运行期 prompt 是数据源 Employees by Organization 自带的,无需自己创建
  • Prompt 字段(逐字):Include Subordinate Organizations、Include Managers、Organization*(必填,选要出数的组织)

"these prompts automatically were built into that data source. So, I did not have to um create these prompts. And this allows the user to select um whichever organization they want the data for."— 这些 prompt 已经自动内置在那个数据源里了,我不用自己造;它让使用者去选自己要哪个组织的数据。

1:12:00

报表结果:18 行现薪与拟薪

报表结果:18 行现薪与拟薪
  • 报表名 RM Salary by Org,结果 18 items,列:Employee / Employee ID / Effective Date / Base Pay - Current / Base Pay - Proposed
  • 回显 prompt:Organization = HR Services Department、Include Subordinate Organizations = Yes、Include Managers = No
  • Effective Date 均为 04/01/2020;示例行 Maria Cardoza(21006) 125,755.00→130,156.00、Norman Chan(21012) 107,618.00→110,308.00、James Moore(21014) 100,876.00→103,398.00
  • 关键概念:current/proposed 是相对这笔 4/1 生效的交易——current=变更前工资,proposed=该变更事件里录入的新工资,非「实时当前工资」

"the words current and proposed, they're with the respect to the transaction. So, this transaction was effective on 4/1."— current 和 proposed 这两个词是相对于这笔交易而言的,而这笔交易在 4/1 生效。

1:15:30

客户报表规格上半

客户报表规格上半
  • 客户真实报表(Excel 规格):Report Name Compensation Change Report for Payroll -APAC,Type Advanced,Data Source Compensation Changes,PBO Employee Compensation Event
  • 用途:给 APAC 区 payroll partner,按她选的 pay period 看该时段全部薪酬变更
  • Data Source Description 原文:Accesses Employee Compensation Event as the primary object and returns one row per compensation change
  • Columns(前段):Worker 对象取 Worker(列头 override Employee)/Employee ID/Location/Region;Employee Compensation Event 取 Compensation Change/Effective Date/Date and Time Completed/Status/Business Process Reason(Base Pay Current-Amount→Current Base Pay)/Base Pay Current-Frequency
  • 运行期 prompt:Pay Period Start Date、Pay Period End Date、Completed By/Last Run Date、Home Country

"Now, I'm going to share with you an actual report I had to build for a client. It's in Excel format. So, let me pull that up and put that on the screen. So, the use case was that for the payroll partner who was in APAC region, they wanted to see all of the compensation changes within a particular time frame."— 现在给你们看一张我实际为客户做的报表,是 Excel 格式。用例是:APAC 区的 payroll partner 想看某个时间段内发生的所有薪酬变更。

1:19:30

客户报表字段下半

客户报表字段下半
  • 关键字段 Date and Time Completed=最终审批人完成交易的时间,实为审批日期,讲师建议 Column Heading Override 改成 Date Approved
  • 追加列:Base Pay Proposed - Amount→Proposed Base Pay、Base Pay Proposed - Frequency→Frequency、Worker|Compensation Plans Effective→Compensation Plan(此处换了业务对象取 plan 明细)
  • Status 列显示交易 pending 还是 approved;Business Process Reason 给出变更原因
  • 运行 prompt 补齐:Home Country、Location、Region(按区域/国家/地点跑)

"one interesting field is date and time completed. So, this actually means um I should have actually override this heading and and change it to date uh date approved. Because the the date and time when this transaction completes is when the final approver completes it."— 有个有意思的字段是 Date and Time Completed……交易完成的时间就是最终审批人把它审完的时间,所以其实应该把列头改成 Date Approved。

1:26:30

Prompts 运行期日期

Prompts 运行期日期
  • Prompts 标签:可给 filter 用到的字段建运行期 prompt,用户在跑报表时输入值作为过滤
  • 比较值来源三选一:Value specified in this filter(硬编码)/ Prompt the user for value(运行期填)/ Value from a field
  • Runtime Date Prompts 已带 Effective Date*、Entry Date*(默认 Use date and time at runtime)
  • Prompt Defaults 表列:Order、*Field、Prompt Qualifier、Label for Prompt、*Default Type、Default Value、Required、Do not Prompt at Run(本例 0 items)
  • 可勾 Display Prompt Values in Subtitle 让运行条件显示在报表副标题

"if I selected prompt then on the prompts tab I will have to add that as a prompt. So, then this field will be presented to the user at run time and then they will enter a particular date. And then that will be used as a filter."— 如果我选了 prompt,就得在 Prompts 标签里把它加成一个 prompt;这样这个字段会在运行期呈现给用户,让他们填一个具体日期,再拿它作过滤条件。

1:28:30

Region 报表字段详情

Region 报表字段详情
  • 讲师现场又踩 Optimized for Performance 的坑(this checkbox got me again),需再取消勾选才选到 Compensation Changes
  • 第二张报表 Compensation changes for Region:Type Advanced,Data Source Compensation Changes,PBO Employee Compensation Event
  • Worker 业务对象字段弹窗(511 个结果)中 Worker 字段:Field Source Workday Delivered、Field Type Self referencing instance、Related Business Object Worker
  • Worker 字段 Category:Benefits Eligibility / Name / Payroll / Time Off;Authorized Usage 含 …/ Default Areas / Security Attribute - System User
  • 用 worker 业务对象取人员基础信息(含 worker location 列)

"we'll just call it compensation changes for region. We'll call it It's going to be an address report. And we're going to use um compensation changes as the data source. Oh. See, this checkbox got me again. I I went to start typing in my data source, and I have to uncheck that."— 就管它叫 compensation changes for region,用数据源 Compensation Changes。哎,又被这个勾选框坑了一次,一输数据源才发现还得先把它取消勾选。

1:32:00

Filter 两段日期 prompt

Filter 两段日期 prompt
  • 在 Filter 标签给实例加条件:对字段 Date and Time Completed 建两段边界,做成日期区间
  • Row1:And | Date and Time Completed | greater than or equal to | Prompt the user for the value | Prompt #1
  • Row2:And | Date and Time Completed | less than or equal to | Prompt the user for the value | Prompt #2(即审批完成日期落在起止两 prompt 之间)
  • 用 Prompt the user for value 而非硬编码,让用户跑报表时选审批时间段;其余字段讲师称课后补

"Date So, this one is going to be less than or equal to. And once again, we're going to prompt it... I could do a quick test to see if it's working. So, I got all of these prompts by default. Uh based on the prompts that are already there on that uh on that data source."— 另一个条件就设成小于等于,同样让用户 prompt 来填。然后我快速测一下能不能跑——默认就带出了这些数据源里已有的 prompt。