Not really, if you are dynamically creating attributes then referencing them within the workspace the workspace is no longer dynamic and would need to be updated each time it's run.

It is however possible to set attributes without exposing them and then create a schema so the output can be written without exposing the attributes at all. If you could provide a bit more information about what you are trying to acheive someone may be able to advise further.

Example

Dynamic_table_example.fmw

Is it possible to use the bulkattributerenamer to rename the attributes based on a look-up?

E.g. Table 1 with generic attribute names

E.g. Table 2 automatically created table (date values will update on each run)

So I would like to use Table 2 as a look-up for the bulkattributerenamer. Renaming the Attributes in Table 1 with the Auto-generated date from Table 2 where the Attribute Name in Table 1 matches the Attribute Name value in Table 2.

Hi @kat18, would it be possible for you to share your workspace (.fmw)/screenshots of what you have achieved so far, along with some sample data, so we can take a closer look at it? Thanks!

The easiest way to work with the data is to not Cross tabulate at all.

Instead of having a table with Attributes of "Name", "Feb-20", "Mar-20" etc..... have a 3 attribute table like this:

Name, Month, Value

So to assign a value to a Name of say "Kat" and the Month of "Feb-20", then use something like an AttributeCreator that assigns a Conditional Value WHERE Name="Kat" AND Month = "Feb-20", or similary use the Month value inside a formula that takes this as an input to calculate the value for that Name, Month combination.

To assign values to all months at once then use something like StatisticsCalculator with GROUP BY set to "Name", "Month", or similarly use something like the InlineQuerier to do Avg, Min, Max, Count etc. with a SELECT Statement GROUP BY also set to "GROUP BY Name, Month"

It is far easier to perform calculations on data if it is kept Normalised like this instead of Cross-Tabbing it. I know that is how many people are used to viewing these tables inside Eg. MS Excel, but the trick to representing 2 dimensional tables inside data processing programs like databases and FME is to store the 2 dimensions as 2 different Fields/Attributes rather than make the 2nd Dimension attribute values as Field Names/Attribute Names. The golden rule is to save the Cross Tabulation to the end when outputting to the final table, which is usually only done for presentation/readability purposes. To expose the attributes on the final table is either an AttributeExposer or to write dynamically as @ebygomm has set out.